Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 456371 - httpd unable to handle ab -n 1500000 -c 500
Summary: httpd unable to handle ab -n 1500000 -c 500
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: httpd
Version: 4.6
Hardware: i386
OS: Linux
Target Milestone: rc
: ---
Assignee: Joe Orton
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2008-07-23 07:45 UTC by Qian Cai
Modified: 2008-07-24 10:56 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-07-24 10:56:04 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Qian Cai 2008-07-23 07:45:44 UTC
Description of problem:
On (i386), ran

# ab -t 7200 -n 1500000 -c 500 -e load_test_proper.csv

This is ApacheBench, Version 2.0.41-dev <$Revision: 1.141 $> apache-2.0
Copyright (c) 1996 Adam Twiss, Zeus Technology Ltd,
Copyright (c) 1998-2002 The Apache Software Foundation,

Benchmarking (be patient)
Completed 500000 requests
Completed 1000000 requests
apr_recv: Connection reset by peer (104)
Total of 1140857 requests completed

Changed the command to -c 300 worked without any problem. I have seen this
problem on i386 only so far.

Version-Release number of selected component (if applicable):
Both client and server were RHEL4-U6 GA distros.

How reproducible:

Comment 1 Joe Orton 2008-07-23 09:02:18 UTC
Were you using the default httpd.conf?  That has:

MaxClients       256

so it is unsurprising that you see ab errors for concurrency of 500.

Comment 2 Qian Cai 2008-07-23 09:39:34 UTC
Yes, I was using that default setting.

Comment 3 Joe Orton 2008-07-24 10:56:04 UTC
This is not entirely surprising behaviour then.  Use a smaller concurrency
setting or increase MaxClients and ServerLimit.

Note You need to log in before you can comment on or make changes to this bug.