On Tue, 12 Aug 2003, hammett wrote: > Premature optimization or foreseeing?
Premature, since you're not backing up your claims with anything solid. Your claims seem to be basically that it takes time to load all the classes in a jar. However, we only pay a price if a class is loaded that wouldn't have been loaded otherwise. If your server, when it has started normally, has loaded all classes in the jar, then it doesn't matter if we load them incrementally through the whole startup sequence, or in one go at the start. So basically, the performance penalty boils down to: What is the percenage of classes in a typical system that never get loaded? If you have a low percentage, then loading all classes at startup has low penalty, if you have a high percentage, then you'll start paying a penalty. So what is the ratio of actually used classes to the total number of classes? /LS --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
