Hi Chris,
Am 03.08.2010 22:08, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 8/3/2010 10:55 AM, Peter Buning wrote:
we tested our tomcat 5.5 server (Debian system) with the apache
benchmark tool. We send requests for a small png-file (300 bytes).
Thanks for your reply!
Keep alive is disabled. The slower response times are seldom, nearly 0,1
% of all the requests. The tests were done with a concurrency of 1.
I think, as Chris replied, it 's another process of the OS.
the server.xml:
Server port=8005 shutdown=SHUTDOWN
Listener
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 8/4/2010 3:33 AM, Peter Buning wrote:
Hi Chris,
Am 03.08.2010 22:08, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 8/3/2010 10:55 AM, Peter Buning wrote:
we tested our tomcat 5.5 server
Thanks again!
Am 04.08.2010 15:38, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 8/4/2010 3:33 AM, Peter Buning wrote:
Hi Chris,
Am 03.08.2010 22:08, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On
Hello,
we tested our tomcat 5.5 server (Debian system) with the apache
benchmark tool. We send requests for a small png-file (300 bytes).
Nearly all requests were done in 0 or 1 milliseconds. But there were a
few request which needed more than 10 ms and the slowest request needed
106 ms.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 8/3/2010 10:55 AM, Peter Buning wrote:
we tested our tomcat 5.5 server (Debian system) with the apache
benchmark tool. We send requests for a small png-file (300 bytes).
Nearly all requests were done in 0 or 1 milliseconds. But there
Peter Buning wrote:
Hello,
we tested our tomcat 5.5 server (Debian system) with the apache
benchmark tool. We send requests for a small png-file (300 bytes).
Nearly all requests were done in 0 or 1 milliseconds. But there were a
few request which needed more than 10 ms and the slowest
