tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Econopouly" <>
Subject Re: More data on Jakarta Tomcat vs Resin.
Date Wed, 30 Aug 2000 16:48:08 GMT

There are applications available for that kind of thing, yes.
Some people recommend a util called ab, which comes with apache.

I wrote my own for my tests.  Basically, I wanted to simulate
600 applets connected to a servlet via HTTP tunnelling.  So I
just wrote a java app that splits off 600 threads, each of which
connects to the servlet in the same way that the applets ultimately
will, using HttpURLConnection.  Then I wrote another app that generates
messages to be sent to those pseudoapplets, one every minute.  The message I 
send is just the "ones" digit of what minute it is - i.e. at 1:53:00 exactly 
I send the message "3".  Finally, in the app that has the 600 threads, aka 
the pseudoapplets, the main thread prints out the last message received by 
all threads, along with the current time, once per second.  That way I can 
see how long it takes for the message to reach all the pseudoapplets.

hope that helps

>From: "Richard Diaz" <>
>To: <>
>Subject: Re: More data on Jakarta Tomcat vs Resin.
>Date: Tue, 29 Aug 2000 10:56:52 -0700
>Thanks for the info, it's very valuable!
>How does one stress test? Are there applications that can call and execute
>JSP pages multiple times? Where can I get that application? I'd like to run
>that against my servers.
>I too am going to make a servlet that pushes to applets, any help/info on
>that would be greatly appreciated!
> > Thought this might interest y'all.
> > I'm stress-testing a couple servlet engines using a servlet I've
> > written that does real-time push to client applets.  In order to satisfy
> > requirements, it has to maintain concurrent open TCP connections (in the
> > form of HTTP requests that block) to a large number of applets (I've 
> > testing with 600 - hoping to go even higher).
> >
> > My tests involve simulating the 600 clients, which all connect to the
> > servlet, and then generating "events" (once per minute) that are
> > pushed to all of them.  I then measure how long it takes for the event 
> > sent to all the clents.  Using Tomcat3.1, it takes about 3-4s.  Using
> > Resin1.1, it takes about 1s!  So for this task, Resin is way faster.
> >
> > But Tomcat is alot more stable than Resin (again, for this task).
> > Basically, Tomcat runs safely for 40 - 160 hrs.  Resin shuts down after
>2 -
> > 6 hours.  Both are running on the same machine - RedHat Linux 6.1 with 
> > sun jdk1.2.2, both in standalone mode.
> >
> >

Get Your Private, Free E-mail from MSN Hotmail at

Share information about yourself, create your own public profile at

View raw message