Return-Path: X-Original-To: apmail-jakarta-jmeter-user-archive@www.apache.org Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3B80195F2 for ; Wed, 21 Sep 2011 22:56:33 +0000 (UTC) Received: (qmail 75867 invoked by uid 500); 21 Sep 2011 22:56:32 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 75839 invoked by uid 500); 21 Sep 2011 22:56:32 -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 75828 invoked by uid 99); 21 Sep 2011 22:56:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Sep 2011 22:56:32 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=FREEMAIL_FROM,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted nor denied by domain of kootsoop@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Sep 2011 22:56:26 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1R6Vi1-0005Fr-HW for jmeter-user@jakarta.apache.org; Wed, 21 Sep 2011 15:56:05 -0700 Date: Wed, 21 Sep 2011 15:56:05 -0700 (PDT) From: kootsoop To: jmeter-user@jakarta.apache.org Message-ID: <1316645765536-4828222.post@n5.nabble.com> In-Reply-To: <1316628868074-4827319.post@n5.nabble.com> References: <4E2D88FA.9090900@gmail.com> <1316535562299-4823146.post@n5.nabble.com> <1316546024995-4823652.post@n5.nabble.com> <1316549536808-4823875.post@n5.nabble.com> <1316610468263-4826253.post@n5.nabble.com> <1316611472710-4826314.post@n5.nabble.com> <1316628868074-4827319.post@n5.nabble.com> Subject: Re: Jmeter Performance using, jmeter-server VS running in the local instance MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Oliver Lloyd wrote: > > Ah, that's different. It's true (or at least I have experienced the same > thing) that if you have JMeter running in Distributed (master_slave) mode > then you can potentially hit an IO bottleneck where JMeter cannot write > multiple results streams to one file quick enough. The workaround - as you > have already seen - is to run multiple instances in isolation and then > append all the results together (and then sort them). Personally, I do > this all the time - I have it as a habit. > Thanks, that definitely makes sense of what I am seeing and gives me the way forward. I've been running three clients on separate machines from the command line now, just dumping to a JTL file. Then loading it up in a GUI client to collate the results afterwards. That gives me what I need. > PS. That is all independent of using the CTT. That's just useful for > creating repeatability / reaching a defined load. etc. > Understood. I'll see what I can do to use the CTT as a baseline "selectable" load that other tests can run on top of. Thanks again for the feedback! -- View this message in context: http://jmeter.512774.n5.nabble.com/Jmeter-Performance-using-jmeter-server-VS-running-in-the-local-instance-tp4631144p4828222.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