Clapham, Paul skrev den 26-09-2007 00:37:
The problem is, on some machines this hot-deployment procedure takes a
ridiculously long time. At present the application is less than 200
classes and the jar file is about 300K. On one machine it takes about a
minute and a half to do this for each task, whereas on another machine
it takes less than 10 seconds. And when you multiply that by 50 or 100
tasks, you can't even call it lukewarm deployment.
There is a verification task that must be run to ensure that the code is not evil. The result of this is cached so it is only the first time.

I have found that the IBM documentation saying that the fastest environment is the just-in-time-compiler is right. You should set the java property "java.compiler" to "jitc". It is more aggressive than the Sun HotSpot.

Try this and see if things change.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.