On Wed, 9 Mar 2005 14:28:53 -0500, Nathan J. Mehl <[EMAIL PROTECTED]> wrote: > In the immortal words of sebb ([EMAIL PROTECTED]): > > Doesn't one need an RMI process on each server node? > > If not, how does the client connect to the server without an RMI process? > > That's actually what I was doing, e.g: > > tester1: rmiregistry & > jmeter-server & > jmeter -n -r -t mytestplan.jmx > > tester2: rmiregistry & > jmeter-server > > I think Peter was suggesting that tester1 could run the testplan > in-process while running it remotely on tester2 via rmi?
Yes, that would make sense - less overhead, as the client does not need to communicate with a jmeter server on the same node, and there is no need to run either RMI or the server on the same node ... > > If you can't get this working, try using batch (non-GUI) mode on the > > two "server" nodes. > > As above, that's actually what I was doing. What I meant was to copy the test plans to the two nodes, and run each independently, i.e. jmeter -n -t mytestplan.jmx -l mytestplan.jtl on each node independently. Running the client in non-GUI mode helps, but there is still the extra overhead of the RMI process and the sample results being passed back to the client. > > This uses fewer resources. Unless you need two different IP addresses, > > you might even find that the test could be run from just the one node. > > And the JTL files can be fairly easily combined. > > Hm. I don't "know" that I need both nodes -- but I'm trying to > simulate loads of 200, 400 and 600 users on an http-request testplan > that sequentially loads 7 urls per thread. Is it reasonable to expect > a single server (2.4ghz P4-HT) to do that? > > > It helps if the various node server clocks are synchronised - even for > > client server mode. > > Yeah, running ntpd everywhere. :) > > -n > > ------------------------------------------------------------<[EMAIL > PROTECTED]> > "We build our computers the way we build our cities -- over time, without a > plan, on top of ruins." (--Ellen Ullman) > <http://blank.org/memory/>---------------------------------------------------- > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
