F
frank.meulblok
Guest
[quote user="Lieven De Foor"] In my specific case the class will have a couple hundred instantiations, so perhaps in that case the single static vs multiple instance method "instantiations" does have a noticeable impact? [/quote] That'd mostly depend on the number and type of instance members, and code in instance constructors. Makes things hard to predict. But if for example you decided the instance Constructor is a good place to pull a few thousand records into an instance-member temp-table, then yes you probably would see a substantial impact. If on the other hand you have only a small handful of properties and a default constructor, even a few hundred instantiations probably won't add more than a few milliseconds to the total running time. As far as loading the actual code goes: AFAIK any method, regardless of STATIC status or access level, is just another r-code Action segment. So you won't see a difference there. Well, actually, there might be a negative impact there if -mmax and -d are poorly tuned, because classes with static members would not release the resources they claim there. Thus more statics may lead to more swap space in the rcd* file being used, other r-code being unloaded and reloaded more frequently, etc.
Continue reading...
Continue reading...