Originally posted by Ernest Friedman-Hill:
The first thing I'd do is track down the total size of the applet download. If it's a huge amount of code, perhaps there's a way to cut it back.
If it's not the download, then find out what's going on while that progress bar is ticking along. What work is being done? Perhaps there's a way to do it faster.
Originally posted by Ulf Dittmer:
The imports you list above are all part of the JRE - they don't need to be downloaded, and thus won't prolong the download/startup time. Are you using 3rd party libraries that do need to be downloaded? Or other resources like images or data files?
Originally posted by Ulf Dittmer:
The imports you list above are all part of the JRE - they don't need to be downloaded, and thus won't prolong the download/startup time. Are you using 3rd party libraries that do need to be downloaded? Or other resources like images or data files?
Originally posted by Ernest Friedman-Hill:
"The DataBase with the XML files has to be accessed".
There's an important place to look. Database transactions can be slow, whether you're really talking to a remote database directly from an applet, or if there's a middle tier on the server that's talking to the database, and then the applet is talking to that middle tier.
The stuff you say about "all the different kinds of Java" and that this somehow causes a lot of hunting around for versions of classes doesn't make any sense, nor is it anything you need to worry about.
In any case, blindly making small changes isn't going to help, nor is changing from Swing to AWT. The only thing that will help is study and measurement. If you need to speed things up, then you need to find out where the time goes.
I hired a bunch of ninjas. The fridge is empty, but I can't find them to tell them the mission.
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|