RE: Tomcat 4/5 Clustering.

2003-10-10 Thread Nathan Christiansen
>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]



Re: Tomcat 4/5 Clustering.

2003-10-10 Thread Filip Hanik
>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


- Original Message -
From: "Nathan Christiansen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 10, 2003 10:17 AM
Subject: Tomcat 4/5 Clustering.


Filip,

Thanks for the link to your site on Tomcat clusters.

Are there any preliminary results about cluster size vs. replication traffic
and limitations?

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.

It was this reason alone that I stopped using the session object to store
session info. I store my persistent objects to a MySQL database, using a
session cookie as the key to the database row.


Are there plans to support Session Object storage in a database (like my
method of storing persistent objects)?

This would allow massive scalability in the cluster, since the 'dirty'
session object only needs to be sent to one place instead of to all the
Tomcat servers in the cluster.

I realize that this introduces a problem in that every single server in the
cluster needs to be running the same version of Tomcat in order to have
session objects serialize and deserialize properly. Or that you will need to
use another storage format other than simple serialization and
deserialization.

-- Nathan Christiansen
   Tahitian Noni International
   http://www.tahitiannoni.com


-Original Message-
From: Filip Hanik [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2003 10:20 AM
To: Tomcat Users List
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Clustering Tomcat - Loadbalancing and Failover


http://cvs.apache.org/~fhanik/

> how are session states replicated?

once, after the entire request is completed. If the session is not dirty, no
replication will be done

Doesn't use java groups, instead pure UDP/TCP.

Filip


-- Nathan Christiansen
   Tahitian Noni International
   http://www.tahitiannoni.com

-
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]