>It has been done for years, PersistentManager does that already. It >is a pretty slow way of replication
Thanks, I'll look at PersistentManager. Slow? I guess so. I have eliminated most of the database overhead by using DBCP to create a connection pool. However... Using my method of persistence, on my development PIII 500Mhz 256MB RAM RH Linux 7.1 box under a JMeter simulated 25 user load, I only got 340 pages per minute on some simple JSP pages and 100 ppm on the most computationally intensive JSP page. I am curious how well my app will perform on our production boxes. -- Nathan Christiansen Tahitian Noni International http://www.tahitiannoni.com -----Original Message----- From: Filip Hanik [mailto:[EMAIL PROTECTED] Sent: Friday, October 10, 2003 11:22 AM To: Tomcat Users List Subject: Re: Tomcat 4/5 Clustering. >Are there any preliminary results about cluster size vs. replication traffic and limitations? if you have a GIGA network, you can go pretty wild! >If I remember right, the limit for load balancing clusters using an older method was about >6 servers in your cluster before the session object replication became the bottleneck. all I said was that I have seen it work on 6 servers, however, with any cluster, using all-to-all replication, I recommend keeping the clusters smaller. :) >Are there plans to support Session Object storage in a database >(like my method of storing persistent objects)? It has been done for years, PersistentManager does that already. It is a pretty slow way of replication >Or that you will need to use another storage format other than simple serialization and deserialization. Run the same version, run different and it may/may not work Filip --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
