I believe (intuition, haven't checked) it is the latency the TCP adds
to the setup which messes up with the threads scheduler (i'll
ellaborate...)
When you are in Tomcat only, between the http header coming in (IO)
and you sending a response (again IO) you can usually get away with a
Yuval Perlov wrote:
Out tomcat servers are handling around 30K SSL hits every 5 minutes with
very little effort (10% cpu average on a dual core machine, good
response time).
We tried to put in httpd in front thinking we can squeeze out better
performance and memory consumption.
The system just
I know the latest edition of the O'Reilly Tomcat book by Brittain and
Darwin strongly advocates the use of standalone Tomcat as opposed to the
traditional httpd-Tomcat approach, but this seems to be somewhat of a
paradigm shift for most people. I'm interested in hearing what the
wider
On Mon, Apr 28, 2008 at 11:27:09AM -0400, Larry Prikockis wrote:
I know the latest edition of the O'Reilly Tomcat book by Brittain and
Darwin strongly advocates the use of standalone Tomcat as opposed to the
traditional httpd-Tomcat approach, but this seems to be somewhat of a
paradigm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry,
Other than Mark's comments...
Larry Prikockis wrote:
| 1) Any thoughts on why the Apache SSL - Tomcat combination should be so
| much slower?
If your transactions are short, it's certainly possible that most of the
time is taken up by
Out tomcat servers are handling around 30K SSL hits every 5 minutes
with very little effort (10% cpu average on a dual core machine, good
response time).
We tried to put in httpd in front thinking we can squeeze out better
performance and memory consumption.
The system just couldn't handle
Mark H. Wood wrote:
On Mon, Apr 28, 2008 at 11:27:09AM -0400, Larry Prikockis wrote:
Specifically, we have a webapp on a Windows 2003 server that utilizes
Apache 2.2 SSL as a frontend and mod_proxy_ajp to send requests to Tomcat
5.5.17 (on the same server). By eliminating the Apache frontend
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry,
Larry Prikockis wrote:
| Mark H. Wood wrote:
| That's certainly worth thinking about. What exactly do you mean by
| performance?
|
| good point... shoulda been more specific-- we were mainly looking at raw
| connections per second and
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry,
Other than Mark's comments...
Larry Prikockis wrote:
| 1) Any thoughts on why the Apache SSL - Tomcat combination should be so
| much slower?
If your transactions are short, it's certainly possible that most of
