You may want to find out where the bottlenecks are before deciding on clustering or lb tomcat. For instance, if the bottleneck is your backend database, clustering tomcat won't help at all. One easy way to find out the bottleneck is to turn on the debugging or just use the operating system monitor to monitor the CPU utilization (assuming tomcat and the backend database are on different machines).
ND -----Original Message----- From: BB Commish [mailto:[EMAIL PROTECTED] Sent: Friday, November 18, 2005 12:50 PM To: users@tomcat.apache.org Subject: Managing concurrent high memory processes We have a Struts application running on Tomcat where a few actions within the app can invoke processing that consumes 300+ MB of RAM and can run for several hours. The issue is how to make the application more scalable to accommodate multiple concurrent 'high load' processes and also make better use of servers with available RAM beyond the jvm limits (we have used both Sun and JRockit jvms - typically on Win2k3 as per customer requirements). Would Tomcat clustering/load balancing be suited to this problem? Or is it more geared to managing high volumes of requests rather than just dealing with certain high load requests that need special attention? We have also considered spawning a separate jvm instance (or retrieving from a pool more likely) to handle each high load request with the 'normal' requests being handled within the jvm running Tomcat. Is this a feasible option? I will appreciate any comments. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
