Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <user@jmeter.apache.org>
Received-SPF: pass (athena.apache.org: domain of robertoschwald@googlemail.com
 designates 209.85.214.52 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Enhancement request for registering remote servers
From: Robert Oschwald <robertoschwald@googlemail.com>
In-Reply-To: 
 <CAOGo0Vasdup+evqDq-n4Tmi6z5jY+ZcDc0Ygy4ub0Tx5GwDH8A@mail.gmail.com>
Date: Fri, 2 Aug 2013 11:55:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1397EFFC-5747-492F-89AC-1BFF9ACCE741@googlemail.com>
References: <628C555D-EA8D-4ACD-8552-99B60A24C6E7@googlemail.com>
 <CAOGo0Vasdup+evqDq-n4Tmi6z5jY+ZcDc0Ygy4ub0Tx5GwDH8A@mail.gmail.com>
To: "JMeter Users List" <user@jmeter.apache.org>


>> Registering remote servers by property file is very static.
>=20
> Can also do it on the client command-line by defining the appropriate =
property.
>=20

The idea is, to create the test plan, select the servers to run the test =
on and store that within the test plan.
This way, it would also run on the commandline (and ant).=20
Advantage would be, to have a cluster of servers on a per-plan base and =
to ease server registration.

> Also remember that the same test plan is sent to each remote server,
> so changing the number of servers will affect the load that is
> generated.

exactly. This means, if you register a new server in the property file =
(e.g. you need it in another test plan), it currently affects all =
existing plans, except if you dynamically register via commandline =
parameter, right?=

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org