Hi Mike,
I can't correct you, since my last post made it obvious that I am new to
both, tomcat and JSP. My point is, that it is not clear to me where high
loads start and low loads end. Maybe the subject was misleading, I meant
'possibly relative high loads for tomcat'. If you think that tomcat is
not capable of handling that type of project I described, thanks for the
information. (that was my intention in the first place, now there is
still time left to evaluate alternatives like Orion, JRun or Resin).
Regards,
Michael
-Ursprüngliche Nachricht-
Von: Wills, Mike N. (TC) [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 12. August 2002 23:30
An: 'Tomcat Users List'
Betreff: RE: tomcat performance and load capability
Correct me if I am wrong, but isn't Tomcat designed for low loads not
heavy
loads? I think you may need to look into a commercial product.
Bealogic
and
IBM Websphere I hear are good ones.
-Original Message-
From: michael wimmer [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 12, 2002 4:25 PM
To: 'Tomcat Users List'
Subject: tomcat performance and load capability
hi all,
we are trying to migrate our development, at least partually, from
coldfusion to jsp. Our first project is about to start and we are now
a
little bit concerned about the performance.
It is a simple promotion, consisting of 6 JSP pages with access to a
MySql database. DB connectivity is implemented with mm.mysql driver
and
protomatter for connection pooling.
Since the the project will be promoted via radio spots, we estimate up
two 30.000 hits per day with possibly extreme peaks after the spots
have
been broadcasted.
I used JMeter for testing and I came up with the insight that tomcat
has
problems if I start more than 75 concurrent threads. (e. q. 100 users,
going for two rounds ended up with maybe half as many entries in the
database as there were supposed to be). Increasing the 'maxProcessors'
parameter for the connector did not solve the problem, tomcat (version
4.1.8) still stopped at 75 threads only viewing now the higher number
in
the error message 'servlet status'. This problem did not occur when I
ran the same project in the resin 2.1.4 container.
My questions are:
- Is Tomcat capable of that load? (Especially for the peaks, I am not
concerned about the overall load).
- Our provider has uttered that running it on two machines (Solaris),
one containing the apache web server, the other server hosting tomcat
would be the way to do it. Since only a few popup's are HTML and all
other pages have to be handled by Tomcat anyway (I would say more than
80% off all request are for JSP's), I am concerned if it really is a
good idea to have apache forwarding all pages to a different computer.
Since we HAVE to use our providers shared MySql, the database server
was
not part of my performance consideration.
- Which version of Tomcat is recommended (4.0.4 or 4.1.8)?
- Which JDK (1.3 or 1.4) works best with Tomcat.
- Any hints / tips for optimizing the configuration would be highly
appreciated.
Best regards,
Michael Wimmer
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]
For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
