----------------------------------------------------
Please read the FAQ at <http://java.apache.org/faq/>
It has a search feature and all the answers!
----------------------------------------------------
Suppose you call ab with -n 60 -c 60 to simulate a rush of 60 simulatenous
hits on a particular page. With the (c-1) + 1 extra executions, you'll get
120 executions instead of 60 -- which makes sense from what you were saying.
I know that ab will report 60 "complete requests" and not count the other
requests in it's stats. My question is, won't these 60 extra executions
affect the outcome of the results significantly because the server will be
getting hit with twice as many executions?
Thanks,
Kevin
-----Original Message-----
From: Marc Slemko <[EMAIL PROTECTED]>
To: Java Apache Users <[EMAIL PROTECTED]>
Date: Friday, October 08, 1999 12:28 PM
Subject: Re: ab seems to be making extra requests while testing servlets
>----------------------------------------------------
>Please read the FAQ at <http://java.apache.org/faq/>
>It does have a search feature!
>
>We cannot guess what you are trying to do:
>#1. Include version numbers for all software.
>#2. Include relevant configuration settings.
>#3. Include full descriptions of the problem.
>
>Got Linux? Seeing lots of java processes?
><http://java.apache.org/faq/?file=274>
>----------------------------------------------------
>
>On Fri, 8 Oct 1999, Kevin Macclay wrote:
>
>> We're using ApacheBenchmark 1.3a and encountering a rather strange
>> occurance. We understand that the following call to ab means that ab
will
>> simulate 5 concurrent users each making 10 requests for a total of 50
>> requests.
>>
>> ab -n 50 -c 5 "http://www.oursite.com/servlet/OurServlet"
>>
>> The strange thing is that our servlet gets called 55 times -- five extra
>> times more than it should. Is this an ab bug? We're able to measure the
>
>In this case, ab will make a maximum of 5 simultaneous connections,
>and will keep making requests until it gets 50 responses.
>
>That could possibly mean that, at the time it gets the last response,
>there are c-1 other outstanding requests that it had made that it
>will not handle/process the responses from.
>
>That accounts for 4 of the 5. The other one is due to the code starting
>a new request immediately after it finishes one, without checking to
>make sure that it hasn't already hit the request limit. This one is not
>counted either in the stats.
>
>
>
>--
>--------------------------------------------------------------
>Please read the FAQ! <http://java.apache.org/faq/>
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Archives and Other: <http://java.apache.org/main/mail.html>
>Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
