Hi, We have a requirement where in we need keep a class level attribute which holds some constant data and would be used in each method for logging purpose. Now the question is, should that attribute should be static or non-static? which is better from performance point of view? Thanks, Santhosh.
Michael Morris
Ranch Hand
Joined: Jan 30, 2002
Posts: 3451
posted
0
Moving this to the Performance forum.
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius - and a lot of courage - to move in the opposite direction. - Ernst F. Schumacher
Maulin Vasavada
Ranch Hand
Joined: Nov 04, 2001
Posts: 1863
posted
0
hi if they are not likely to change then u can go with, "final static" which would let compiler optimize it more... otherwise, static would be faster i believe as instance variables needs to be accessed from Heap going via the object reference... any better explanations? regards maulin.
Agreeing with Thomas -- even if there were a performance difference, it shouldn't even enter the picture here. The question smacks of premature optimisation. Way premature. - Peter
0
