Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 53879 invoked from network); 27 Dec 2010 15:49:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Dec 2010 15:49:22 -0000 Received: (qmail 10574 invoked by uid 500); 27 Dec 2010 15:49:22 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 10491 invoked by uid 500); 27 Dec 2010 15:49:21 -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 10483 invoked by uid 99); 27 Dec 2010 15:49:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Dec 2010 15:49:20 +0000 X-ASF-Spam-Status: No, hits=3.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RFC_ABUSE_POST,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of asp.adieu@gmail.com designates 209.85.218.44 as permitted sender) Received: from [209.85.218.44] (HELO mail-yi0-f44.google.com) (209.85.218.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Dec 2010 15:49:15 +0000 Received: by yie19 with SMTP id 19so1858274yie.31 for ; Mon, 27 Dec 2010 07:48:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=iyAak8DvKtKcGW/4JM+UEIpetftjNmQJHxEtLKgkd9s=; b=jyOKNwqlioiXS8Cl/CvnhjmC42RybzQmk8ogfoCiL8hgwoPhpTJwcb1ZaXAd8mT8YS lYxcqzyTh0MyClb2XfXop2Prlmf937fBAh/cr4F6VpvIeH6ZYWgBrokoy0KedVej1b10 VVmSuz2Lj53lAPQDOnntangW0+j1NHSPQWHRI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=popELYu6gQbMOjwVGyhVEgLWurTnW/dmmNkdErVZXbeCAT8Hqx06bff+yuJuqQDnTe a+DkJJVAqTxwjiHRjW1HtcHABW+x8bugCC2UdFoZo0OSMN4Axih2Cm+0LffCTzr25Ma4 w0p+MYCfrFKQqfTwg2UJDBqgLuLOX2fdx1e+A= MIME-Version: 1.0 Received: by 10.150.201.6 with SMTP id y6mr1517104ybf.294.1293464934940; Mon, 27 Dec 2010 07:48:54 -0800 (PST) Received: by 10.150.230.19 with HTTP; Mon, 27 Dec 2010 07:48:54 -0800 (PST) In-Reply-To: References: <1293461461444-3319388.post@n5.nabble.com> Date: Mon, 27 Dec 2010 17:48:54 +0200 Message-ID: Subject: Re: Multiple Jmeter Instances From: Adrian Speteanu To: JMeter Users List Content-Type: multipart/alternative; boundary=000e0cd48644fa00ba04986645f2 --000e0cd48644fa00ba04986645f2 Content-Type: text/plain; charset=UTF-8 Hi guys, In addition: a. If you suspect that the server behaves differently when receiving requests from the same IP, you could double check this using the new feature in version 2.4, ip spoofing (available only for the Http Request Http Client sampler). Note that some network admins might not be ok with this practice and it is not recommended unless the test system is isolated from the rest of the work network. b. When testing distributed (even with no server-client config), save the logs (as .csv) to the disk and then load them both, after the test, into a single & clean listener in order to properly compare with the previous results (for example, throughput is tricky unless you aggregate all results, from all jmeter servers instances). Hope this helps. On Mon, Dec 27, 2010 at 5:35 PM, Anthony Johnson wrote: > Hello, > 100 threads is not an over-whelming amount of load from my > experience. The 2 engine results would seem to show that the > botteneck is somewhere in your test plan. > > One common problem is if you use lots of Listeners, I would try > disabling some and see if your test improves on a single machine. For > instance, the "View Results Tree" is very useful, but is also very > heavy. When cutting the test in half and putting on two machines, a > listener type bottleneck would be lessened with extra CPU and less > thread contention. > > if that doesn't help, you may want to include more details about your > test, jmeter version, and environment. An outline of the test would > allow for a lot better insight. > > Good luck, > > Anthony > > On Mon, Dec 27, 2010 at 9:51 AM, alwaysbmore wrote: > > > > I get two different totally different results. When running multiple > JMeters > > instances on multiples machines compared to a single Jmeter instance on a > > single machine. For example, If I'm looking to run 100 concurrent users. > If > > I run all 100 threads from a single machine the results are much lower, > if I > > were to run 50 threads on one machine and 50 on another. Both instances > are > > run separate from each other, not as a master and server. > > > > I suspect, it might have something to do with all my how the server is > > configured to accept request all coming from a single IP Address. > > > > Can anyone one confirm this, and give some feedback on what results > should I > > trust? > > -- > > View this message in context: > http://jmeter.512774.n5.nabble.com/Multiple-Jmeter-Instances-tp3319388p3319388.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 > > --000e0cd48644fa00ba04986645f2--