Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 5387 invoked from network); 21 Oct 2008 14:46:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Oct 2008 14:46:36 -0000 Received: (qmail 69035 invoked by uid 500); 21 Oct 2008 14:46:36 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 69017 invoked by uid 500); 21 Oct 2008 14:46:36 -0000 Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "JMeter Users List" Reply-To: "JMeter Users List" Delivered-To: mailing list jmeter-user@jakarta.apache.org Received: (qmail 69004 invoked by uid 99); 21 Oct 2008 14:46:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Oct 2008 07:46:36 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates 216.239.58.188 as permitted sender) Received: from [216.239.58.188] (HELO gv-out-0910.google.com) (216.239.58.188) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Oct 2008 14:45:25 +0000 Received: by gv-out-0910.google.com with SMTP id i36so420426gve.24 for ; Tue, 21 Oct 2008 07:46:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=tDLegm7LDXmmLnf4IM4ZxKIWBgR5yAKUUvJeCI6wFQs=; b=giwEP8yqNzz6cmy5WkEl5LX7uds/bBhQxHbQ0IjlP14+SJNcUuzJ2XjQ4K6OYk6F0Q W4S9mrjfu6pSESjQR54J+L2daML+eIe2vgjl1xxLPKV/6pYbzceMq9YOe2Kt+/G+ZDK5 xTeDs/sqLQ/3k0GkJdo7OXL96uTHtULflHMS0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=mDRTVtHD1DzUOcopio/WWTjbmtdUlne2pOcNvMppYUYF4ZTCJaO4drowxB7WR7AunI qds7D3aHI1lCrXndG9QizWeS1AdO5wEddVR08RQ81ev7bVqXj4ayPDNNpYg1vBfHtam6 RKkw6HGDNas7BJUqe/GBfBWd3rmQXeeZXBCBE= Received: by 10.86.63.19 with SMTP id l19mr7989794fga.60.1224600362741; Tue, 21 Oct 2008 07:46:02 -0700 (PDT) Received: by 10.86.1.2 with HTTP; Tue, 21 Oct 2008 07:46:02 -0700 (PDT) Message-ID: <25aac9fc0810210746r64b78538v75f2ce8d7692403c@mail.gmail.com> Date: Tue, 21 Oct 2008 15:46:02 +0100 From: sebb To: "JMeter Users List" Subject: Re: Extrapolating performance data to a customer base In-Reply-To: <20075112.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20075112.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org On 20/10/2008, Ivan Rancati wrote: > > I apologize for the slightly off topic post, but I guess it's a topic that > performance testers often encounter. > > In general, the issue is: after running some tests, I now know that a Web > server farm can serve x concurrent customers in an average of y seconds per > customer. The maximum response times are also very important for a human user. What happens when the load increases? Does the service degrade gracefully? > What is a reasonable formula to extrapolate this number to a customer base > that can be served by this web farm without degradation of performance? This will depend an awful lot on what the application is used for. For example - do customers need to use it every day? Are there special events that might cause a sudden rise in traffic? Do you have control over such events (e.g. a special promotion)? > I guess there are some general assumptions, such as: > - there are less users at night Night depends on where the customer is located. > - there are less users during weekends Likewise - for some cultures Sunday is a day of work. > - the load can be assumed to be uniformely spread during the peak times That is very unlikely to be the case, but you might be able to put some min and max bounds on the traffic. > - ... > > Any actual statistics on how the customer requests are spread and/or > practical examples of how other people calculated this would be appreciated. > If you have access to server logs for the actual (or a similar) application, then that would provide a lot of useful data. > thanks > Ivan > > > > -- > View this message in context: http://www.nabble.com/Extrapolating-performance-data-to-a-customer-base-tp20075112p20075112.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org