Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 66981 invoked from network); 23 Jul 2010 05:58:38 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Jul 2010 05:58:38 -0000 Received: (qmail 89324 invoked by uid 500); 23 Jul 2010 05:58:37 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 88945 invoked by uid 500); 23 Jul 2010 05:58:34 -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 88937 invoked by uid 99); 23 Jul 2010 05:58:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jul 2010 05:58:33 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [80.150.73.7] (HELO mail.exedio.com) (80.150.73.7) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jul 2010 05:58:25 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.exedio.com (Postfix) with ESMTP id 7FFF231A40C; Fri, 23 Jul 2010 07:58:05 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.exedio.com Received: from mail.exedio.com ([127.0.0.1]) by localhost (mail.exedio.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DQ6EdJxn9uDZ; Fri, 23 Jul 2010 07:58:05 +0200 (CEST) Received: from [10.20.20.116] (pc16.dd.exedio.com [10.20.20.116]) by mail.exedio.com (Postfix) with ESMTPSA id 4578931A183 for ; Fri, 23 Jul 2010 07:58:05 +0200 (CEST) Message-ID: <4C492FA9.8030109@exedio.com> Date: Fri, 23 Jul 2010 07:59:05 +0200 From: Karsten Gaul User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1 MIME-Version: 1.0 To: JMeter Users List Subject: Re: DB crash References: <4C48356A.1020906@exedio.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi sebb, > As your test plan is calling the database via the web application, in > theory enough users of the application can cause the same problem. > > You have proved that the web application can bring down the database > (which is useful to know). > > Whether it is possible for this to occur when not using JMeter depends > on how close the test plan load is to what the application is intended > to support. > > Use application logs to gather stats on the page requests made by > actual users, and compare those with the load generated by JMeter. > Adjust the JMeter test plan as necessary to reflect the target load. > > You also need to look at the web application to see if some of the SQL > can be changed to reduce the database load. Actually, what I did was taking REAL data from the logs in order to replay these with jmeter. That works fine as long as you edit this data a little (passwords etc.). The test plan is thus as close as I might possibly get to a real user's actions. Four csv files for four different options to get from a log in to the check out. These four ways are then executed by the threads in parallel. However, what I do not know is how the actual live system reacts because I can only test on a less performant development system. Hopefully, the live system is better configured. rgds Karsten --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org