Also consider that using Apache 2.x is front of a farm of tomcats will help you upgrade your configuration to handle more and more users and requests.
For information, I'm using 2 Tomcat 3.3.2 to handle about 350000 XML-RPC requests by days, Apache2 in front handling the GZIP compression. On Tue, 1 Mar 2005 08:01:00 -0500, Peter Lin <[EMAIL PROTECTED]> wrote: > 100 concurrent users don't necessarily mean heavily loaded. Try 5000 > concurrent users or something even higher. Keep in mind the > bottleneck will be your database, so try to figure what 100 concurrent > users means in terms of peak and average concurrent requests. > > in other words. What are the chances all 100 users will send a request > at the same time? I'm gonna guess it's not very likely. If anything, I > would be surprised if 100 concurrent users results in 25 concurrent > requests during peak and 15 during average. In either case, remember > your Network IO will be a major limitation. > > If the application is on a LAN, then you're fine. If it's hosted at an > ISP and you only have 10mb link, it's not going to be able to handle > 25 concurrent requests. If you're hosted at a nice ISP that gives you > a 100mb link, you should be ok. The only real way to know if tomcat > can handle the load and how many servers you need is to write the app > and stress test it. Once you get a good measure of the average > response time, you'll have more information to decide. If you look at > the latest benchmarks I ran, it's going to be hard to find a servlet > container that is significantly better. In fact, I would say 5.5.x is > even with Resin now. > > hope that helps > > peter > > > On Tue, 1 Mar 2005 07:13:37 -0500, Yoav Shapira <[EMAIL PROTECTED]> wrote: > > Hola, > > Numerous users/organizations have reported using Tomcat for that number of > > concurrent users and higher. Achieving good and efficient programming is > > usually the bottleneck. You might also want to try clustering and > > load-balancing your Tomcats. If you don't want to involve Apache you can > > use a Tomcat with the Balancer webapp as your front-end for load-balancing > > requests. > > > > Yoav > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, March 01, 2005 3:52 AM > > > To: tomcat-dev@jakarta.apache.org > > > Subject: Tomcat for professional large scale webapps? > > > > > > Hello, > > > I made very good experiences using Apache Tomcat for small scale webapps. > > > > > > However, I am now thinking of using it for a larger scale professional > > > webapp: > 100 conconcurrent Users. Haevy downloads, ... > > > > > > Assumed that programming is good and efficient, in what kind of > > > difficulties > > > may I run using Tomcat for a larger scale application? > > > > > > Is it a good choice (in terms of scalability, efficiency, memory usage, > > > ...)? > > > > > > My App environment would be: > > > Tomcat 5.x, Struts, Oracle, Lucene > > > > > > Greetings, > > > Joos > > > > > > -- > > > DSL Komplett von GMX +++ Superg|nstig und stressfrei einsteigen! > > > AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > --------------------------------------------------------------------- > 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]
