Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 69696 invoked from network); 17 Apr 2009 07:04:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Apr 2009 07:04:40 -0000 Received: (qmail 77843 invoked by uid 500); 17 Apr 2009 07:04:39 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 77768 invoked by uid 500); 17 Apr 2009 07:04:38 -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 77757 invoked by uid 99); 17 Apr 2009 07:04:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Apr 2009 07:04:38 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Apr 2009 07:04:29 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Lui7M-0001CH-On for jmeter-user@jakarta.apache.org; Fri, 17 Apr 2009 00:04:08 -0700 Message-ID: <23092193.post@talk.nabble.com> Date: Fri, 17 Apr 2009 00:04:08 -0700 (PDT) From: drubix To: jmeter-user@jakarta.apache.org Subject: One thread per instance on distributed system MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: andrew.schrauf@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm attempting to run a load test against our system but because of the way out authentication is set up each user needs a different IP address. I can achieve this using IP aliasing and running multiple instances of JMeter with different local addresses. What I'd like to have happen is this: * Start each slave JMeter instance on a different RMI port and a different local IP address * Start the master JMeter instance which distributes the script to all of the slaves * Have the slaves work through the test script themselves, managing their own authentication and cookies * Repeat the script for a set length of time * Have all the slaves report back to the master who collates the data However, JMeter doesn't seem to work that way by default. After doing some preliminary tests it seems that final results don't necessarily have a correlation between a JMeter instance and the threadgroup it operates in. It seems that JMeter shares the load dynamically rather than just dishing out an entire thread group to each instance. Unfortunately, as the IPs for each thread/instance will no longer match up, this doesn't work for our particular situation. Is there a way to force JMeter to handle each thread with a different instance or, even better, a way to handle IPs (attaching a single username, password and IP address to a single thread) which would get rid of these problems entirely? Thanks for your help, Drew -- View this message in context: http://www.nabble.com/One-thread-per-instance-on-distributed-system-tp23092193p23092193.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