>> "Danny" == Danny Angus <[EMAIL PROTECTED]> writes:
Danny> In my experience hotspot ( -server option on linux) is
Danny> vital to provide enhanced garbage collection, which
Danny> otherwise is totally inadequate under heavy load. Hotspot
Danny> is also faster, providing on-the-fly compilation of often
Danny> used routines into native code.
Danny> My apps die without it, ending with an out of memory
Danny> exception after about 1 million hits.
JDK1.3 without -server (that is, with -client) also uses
Hotspot. Optionally, you can use the old JIT with -classic (which is
equal to the JIT in JDK1.2).
The diff between hotspot-client and hotspot-server is that the server
version goes to greater lengths in optimizing, causing longer run
times the first time and more memory use (which is why it is for
server, not client) but afterwards the code should run faster. How
much faster? I didn't try but there are some benchmarks on the net.
AFAIK both -client and -server should be better than JDK 1.2's
-classic JIT.
Btw I've never had the problems you describe w.r.t. garbage collection
with the "classic" or "client" JIT. This is on Solaris 2.6, there
might be bugs in the Linux case?
Maybe the server garbage collectyor is more aggressive? I'm not aware
of that. I thought that garbage collection (which was bad in 1.1) has
been pretty good since JDK 1.2.
--
Peter Mutsaers | D�bendorf | UNIX - Live free or die
[EMAIL PROTECTED] | Switzerland | Sent via FreeBSD 4.3-stable
