We have had a very perplexing performance issue crop up with Java Web Start. When our application is run in the Netbeans IDE development environment, all the operations run at the normal, reasonable speed that we have come to expect from past experience developing this particular Web Start Application - both in the development environment and as installed through the Web Start deployment mechanism.
For the latest builds however, when the application is packaged and deployed with Web Start, it's performance is vastly degraded compared with how it runs in the Netbeans IDE - it runs approx. 20+ times slower! This includes ALL operations - this does NOT appear to be a loading/initialization problem.
We have just began trying to investigate the problem through run-time profiling, etc., but have not found the answer yet. If anyone has any insight into this problem - maybe, hopefully, have directly experienced the same problem - or has advise on the best strategy for diagnosing it, we would be very grateful.
This could be something as simple as network latency. JWS would indicate a distributed system, which can very well developed on a local environment (both client+server) Is that the case? Are your client/server on different machines? Have you profiled for network latency?
We had the same problems. After many many tests, we can resolve it.
Our application needs somes libraries in form of many jars. Then we decompress all the classes of all the jars and include them in the principal jar. Our application has now only one jar, and the delay is only on the download time. Now, the performance of the application when it begin is the expected.
I expect this would be useful for every one.
Destiny's powerful hand has made the bed of my future. And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop