Re: [WEB400] What happened to rpgenerationx.com?

["Brad Stone" <brad@xxxxxxxxxxxx>]

I disagree.  If when I was surfing I could strip out the
time that it took to connect that would be great.  I've used
JMeter and I think it "cheats".  I wrote a Java version of
my tool using threads (instead of jobs) and got almost
identical results.

Mine measures from request to completion.  That's how
requests work in the real world.  I've used my tool to load
test many servers, and even the pbA server.  And using it
before and after loading PTFs that help it's CGI performance
it was shown to work.

Anyhow, you shouldn't be worried if I show 3 seconds for a
hit, and you show 800 milleseconds.  You should be worried
about the percentage of difference between 1 request and 10
requests.  Not the actual time.

I'm making the requests from a 170 with 1 gig memory and
average load.  It's also a web server for a LOT of web
sites.  10 users shouldn't make much of a dent unless you
have less than 512k memory, full DASD, 2 arms, etc.

Brad
On Tue, 30 Jul 2002 18:19:11 -0600
 "Nathan M. Andelin" <nandelin@RELATIONAL-DATA.COM> wrote:
> Brad,
>
> Just so we're comparing apples to apples, I have another
> suggestion.
> Download a copy of the JMeter stress test tool from
> www.apache.org to do the
> test.  JMeter instantiates client Threads rather than
> Jobs, and if I
> understand correctly measures the time between the
> request and the first
> byte received in order to strip network time from the
> equation.
>
> Also remember that you're hitting a model 170-2290.  It
> doesn't take much to
> drive the CPU utilization to the wall.  Ten users with no
> delay will peg my
> CPU at +++ utilization.  To be accurate, your tests need
> to let my CPU
> breath, as mine did.
>
> Nathan M. Andelin
> www.relational-data.com
>
>
>
>