From owner-freebsd-isp Tue May 4 6:39:32 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mothership.hostresource.com (unknown [216.37.30.11]) by hub.freebsd.org (Postfix) with ESMTP id 7FB8015117 for ; Tue, 4 May 1999 06:38:49 -0700 (PDT) (envelope-from angrick@netdirect.net) Received: from fdc7.fdcredit.com ([216.37.30.62]) by mothership.hostresource.com (8.8.8/8.8.8) with SMTP id IAA22492 for ; Tue, 4 May 1999 08:37:22 -0500 (EST) (envelope-from angrick@netdirect.net) Message-Id: <1.5.4.32.19990504133854.00bb9114@netdirect.net> X-Sender: angrick@netdirect.net X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 04 May 1999 08:38:54 -0500 To: freebsd-isp@freebsd.org From: Andy Angrick Subject: Apache Stress testing Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone know if there is a program available to stress test an apache webserver. Pound it with requests to see how much it can handle and how much of a toll it takes on the server? If there isn't anything like this available, maybe it would be worth considering developing if anyone would be interested in it also. It could be set up so that there are maybe 10 html pages to choose randomly, then fork a bunch of processes to randomly retrieve these pages. Could be configured as to how many processes to spawn, length of test, etc. I could write it, but I would probably need some help. I think this would be very beneficial. It seems like a lot of us are just in the dark as to how much our servers can really handle. If you ever ask someone how many hits or vhosts a server can handle, there is never a definite answer. Too many variables involved. Andy Angrick Host Resource, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message