[httperf] Httperf --failure-status option ignored

Nenad Petronijevic nenad.petronijevic at softserbia.com
Mon Apr 8 06:16:06 PDT 2013


Yeah, I thought so too.

Thanks for your help, Martin.

Regards,
Nenad
On 04/08/2013 03:13 PM, Arlitt, Martin wrote:
> Hi Nenad
>
> In the brief look I took at the source code, I would say that httperf currently can only use one failure-status code.
>
> Thanks
> Martin
>
>
> -----Original Message-----
> From: Nenad Petronijevic [mailto:nenad.petronijevic at softserbia.com]
> Sent: Monday, April 08, 2013 6:11 AM
> To: Arlitt, Martin
> Cc: httperf at linux.hpl.hp.com
> Subject: Re: [httperf] Httperf --failure-status option ignored
>
> Hi Martin.
>
> Yes, I referred to Errors section of httperf output.
>
> I've noticed that it affects Session statistics, but I've thought that it would affect Errors also, since I've been using autobench to generate graphs and it didn't offer information on  number of 5xx responses or sessions.
>
> Thanks for clearing that up.
>
> Do you know if it would be possible to specify multiple --failure-status codes?
>
> Regards,
> Nenad
>
> On 04/08/2013 03:03 PM, Arlitt, Martin wrote:
>> Hi Nenad
>>
>> What do you mean by "Errors always remain 0"?
>>
>> Are referring to:
>> Errors: total 0 client-timo 0 socket-timo 0 connrefused 0 connreset 0
>> Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0
>>
>> I don't expect the "failures" will show up in those, those are unrelated to "sessions".
>>
>> I expect the "failures" will only affect the session statistics:
>>
>> Session rate [sess/s]: min 0.00 avg 0.00 max 0.00 stddev 0.00 (0/1)
>> Session: avg 0.00 connections/session
>> Session lifetime [s]: 0.0
>> Session failtime [s]: 0.0
>> Session length histogram: 0 1
>>
>> In particular, if you have sessions that contain a lot of requests in them, then the session length histogram should look different when you set --failure-status to a commonly occurring response code than if you don't use it (or set it to an uncommon response code).
>>
>> Thanks
>> Martin
>>
>> -----Original Message-----
>> From: httperf-bounces at linux.hpl.hp.com
>> [mailto:httperf-bounces at linux.hpl.hp.com] On Behalf Of Nenad
>> Petronijevic
>> Sent: Monday, April 08, 2013 5:39 AM
>> To: httperf at linux.hpl.hp.com
>> Subject: Re: [httperf] Httperf --failure-status option ignored
>>
>> Hi Martin.
>>
>> This is just an example request with one session.
>>
>> Otherwise, I usually run it with 1000 sessions and most of them fail with larger rate, with status 502, but there are a lot of successful sessions also.
>>
>> Errors always remain 0.
>>
>> Nenad
>> On 04/08/2013 02:31 PM, Arlitt, Martin wrote:
>>> Hi Nenad
>>>
>>> When the response code matches the --failure-status, it causes the session to fail (see src/gen/session.c, seach for param.failure_status). Because this is happening on the first request in the only session, you simply may not notice it happening in the output, since the session failure statistics are rather coarsed-grained.
>>>
>>> Martin
>>>
>>>
>>> -----Original Message-----
>>> From: httperf-bounces at linux.hpl.hp.com
>>> [mailto:httperf-bounces at linux.hpl.hp.com] On Behalf Of Nenad
>>> Petronijevic
>>> Sent: Monday, April 08, 2013 4:41 AM
>>> To: httperf at linux.hpl.hp.com
>>> Subject: [httperf] Httperf --failure-status option ignored
>>>
>>>
>>> Hi.
>>>
>>> When using --failure-status=502 to make sure that 502 errors are reported as errors, it seems that httperf simply ignores this, even though there are 502 responses.
>>>
>>> I've tried with any other status, 200 or 302, which are most common, but nothing happens.
>>>
>>> Errors are always 0, but 5xx are very high.
>>>
>>> Here is the example of the request.
>>>
>>> httperf --print-reply --print-request --hog --timeout=10 --client=0/1
>>> --server=example.com --port=80 --uri=/ --failure-status=401
>>> --rate=200
>>> --send-buffer=16348 --recv-buffer=32696 --wsesslog=1,1.000,sess.log
>>>
>>> And these are the request and response headers.
>>>
>>> SH0:GET /users/6126 HTTP/1.1
>>> SH0:User-Agent: httperf/0.9.1
>>> SH0:Host: example.com
>>> SH0:
>>> SS0: header 82 content 0
>>> RH0:HTTP/1.1 401 Unauthorized
>>> RH0:Server: nginx
>>> RH0:Date: Mon, 08 Apr 2013 09:46:05 GMT
>>> RH0:Content-Type: application/json; charset=utf-8
>>> RH0:Transfer-Encoding: chunked
>>> RH0:Connection: keep-alive
>>> RH0:Status: 401 Unauthorized
>>> RH0:X-UA-Compatible: IE=Edge,chrome=1
>>> RH0:Cache-Control: no-cache
>>> RH0:X-Request-Id: c573ae0cb46922e1180616a8d13253d4
>>> RH0:X-Runtime: 0.001765
>>> RH0:X-Rack-Cache: miss
>>> RH0:
>>> RB0:{"meta":{"status":401,"message":"Invalid OAuth
>>> Request"},"response":{}}
>>> RS0: header 355 content 71 footer 2
>>>
>>> And bellow is httperf output.
>>>
>>> Maximum connect burst length: 0
>>>
>>> Total: connections 1 requests 1 replies 1 test-duration 0.005 s
>>>
>>> Connection rate: 203.9 conn/s (4.9 ms/conn, <=1 concurrent
>>> connections) Connection time [ms]: min 5.0 avg 5.0 max 5.0 median 4.5
>>> stddev 0.0 Connection time [ms]: connect 1.9 Connection length
>>> [replies/conn]: 1.000
>>>
>>> Request rate: 203.9 req/s (4.9 ms/req) Request size [B]: 82.0
>>>
>>> Reply rate [replies/s]: min 0.0 avg 0.0 max 0.0 stddev 0.0 (0
>>> samples) Reply time [ms]: response 3.0 transfer 0.0 Reply size [B]:
>>> header
>>> 355.0 content 71.0 footer 2.0 (total 428.0) Reply status: 1xx=0 2xx=0
>>> 3xx=0 4xx=1 5xx=0
>>>
>>> CPU time [s]: user 0.00 system 0.00 (user 81.5% system 81.5% total
>>> 163.1%) Net I/O: 101.1 KB/s (0.8*10^6 bps)
>>>
>>> Errors: total 0 client-timo 0 socket-timo 0 connrefused 0 connreset 0
>>> Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0
>>>
>>> Session rate [sess/s]: min 0.00 avg 0.00 max 0.00 stddev 0.00 (0/1)
>>> Session: avg 0.00 connections/session Session lifetime [s]: 0.0
>>> Session failtime [s]: 0.0 Session length histogram: 0 1
>>>
>>>
>>> Thanks,
>>> Nenad
>>>
>>>
>>>
>>> _______________________________________________
>>> httperf mailing list
>>> httperf at linux.hpl.hp.com
>>> http://www.hpl.hp.com/hosted/linux/mail-archives/httperf/
>> _______________________________________________
>> httperf mailing list
>> httperf at linux.hpl.hp.com
>> http://www.hpl.hp.com/hosted/linux/mail-archives/httperf/
>
> _______________________________________________
> httperf mailing list
> httperf at linux.hpl.hp.com
> http://www.hpl.hp.com/hosted/linux/mail-archives/httperf/



More information about the httperf mailing list