🚀 go-pugleaf

Out of intellectual curiosity, I disabled the JIT compiler for JRE version
1.1.6 by running my application with the -nojit flag.  Curiously, my
application loaded up 50% faster (2 seconds versus 3), consistently.  

Performance once it was loaded was, to my perception, equal to when I was
using the JIT.  The application involves mostly AWT events, loading dialogs
and frames, scrolling, and connecting to a database.  (I really should try
my application out on a 486-class machine to see if there is a difference
once it's loaded.  Perhaps my Pentium is fast enough in either case that it
blurs the difference together.) 

I am perplexed as to why -nojit would help out the load time, and not
affect the performace.  Perhaps the JIT compiler is better taken advantage
of if the application is doing more integer number-crunching, or something
like that?  

Also, when does the final JIT compilation take place?  Does it natively
recompile the entire set of classes you specify in your classpath before it
loads the program, or does it recompile each class on the fly, as it is
loaded?  If it's the former, that might explain why the load time was
shorter with -nojit.

Any ideas or opinions will be appreciated. Thanks,

Benjamin Rutt
Systems Engineer
City of Bloomington, IN