Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 97398 invoked from network); 12 Jul 2004 12:51:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 12 Jul 2004 12:51:32 -0000 Received: (qmail 75637 invoked by uid 500); 12 Jul 2004 12:51:29 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 75512 invoked by uid 500); 12 Jul 2004 12:51:28 -0000 Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: 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 75498 invoked by uid 99); 12 Jul 2004 12:51:28 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=RCVD_BY_IP,SB_NEW_BULK,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [64.233.170.196] (HELO mproxy.gmail.com) (64.233.170.196) by apache.org (qpsmtpd/0.27.1) with SMTP; Mon, 12 Jul 2004 05:51:25 -0700 Received: by mproxy.gmail.com with SMTP id c3so232653rnb for ; Mon, 12 Jul 2004 05:51:23 -0700 (PDT) Received: by 10.38.163.20 with SMTP id l20mr120280rne; Mon, 12 Jul 2004 05:51:23 -0700 (PDT) Message-ID: <27e674a904071205512a216ed8@mail.gmail.com> Date: Mon, 12 Jul 2004 07:51:23 -0500 From: Peter Lin To: JMeter Users List Subject: Re: Taking too much of time In-Reply-To: <40F20005.30405@d2hawkeye.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <40F20005.30405@d2hawkeye.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I suspect your web application is timing out or return some error. What kind of database is your web application using? How complex is the login process and what kind of authentication is it doing? Have you looked at the server logs to see if it logged any errors? depending on the database you're using 25 concurrent queries may be a piece of cake, or enough to overwhelm it. If you're using something like Sql Server 5/6, 25 heavy weight queries may be enough to kill it. If you're using something like DB2 or Oracle, 25 is nothing. Another thing to consider is what OS are you using for the server? If you're using windows professional, it has a connection limit of 10 concurrent connections inbound. That means you will have to install server to overcome that limit. without more information, it's hard to tell what is causing the problem you see. peter On Mon, 12 Jul 2004 08:50:41 +0545, Niraj wrote: > Hi, > I am doing concurrent load testing in my web application. My Test > plan is 25 users logging at a same time for 100 times (i.e. Thread > Number =25 and Loop Count=100). The whole test plan took 8-10 hours to > execute. But when I see the results (I am using aggregate report and > result tree listener) , it shows that only > 25 in the "count" field of "Aggregate Listener" for particular page i.e > 25/25=1 iteration only in 8 hrs !!! I am wondering is this a normal case > or I am missing something??? > > --Niraj > > --------------------------------------------------------------------- > 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