Tomcat Optimization for Large Applet

[Chris <ch...@us-hampton.mail.saic.com>]

Setup:
Tomcat 5.0.28
JDK 1.4.2_06
W2K

Currently, we are running a rather large applet served from TC.  When 
the first user logs on, TC memory usage jumps up about 60MB.  When 
another user logs on after the first one is finished, the memory doesn't 
really change.  Also, the cpu spikes pretty heavily, but only for about 
10-20 seconds.  The problem that occurs, is that if multiple people log 
on at the same time, the memory spikes for 60MB for each concurrent log on.

1.  Would using ZIP compression help alleviate the problem?  The cpu 
doesn't seem to be as much of a limiting as the memory.  I would think 
that the compression would help users log in faster, thereby helping 
reduce the chances of concurrent log ons.

2.  Is there a way to queue connections so that tomcat will wait until 
it has available memory, thus preventing the OutOfMemory error?  AFAIK, 
once TC gets an OOM error, it won't do anything until it's restarted.

3.  Would upgrading to TC 5.5.x and/or JDK 1.5 help any?

If anyone can think of any other suggestions, I'd appreciate it.  Thanks.

Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org