just for clarification. is you're intent to simulate

1. requests per second
2. concurrent users
3. concurrent requests


if you're trying to simulate 200, 400, 600 users, the equivalent
requests/second is going to be no more than 1/4 of the total count. In
other words.

200 users - max 50 concurrent requests
400 users - max 100 concurrent requests
600 users - max 150 concurrent requests

in this case, a 2.4 ghz system can easily generate that load. you can
look at my benchmark results for tomcat 5.5.4 with 100, 150, 200
concurrent requests for reference.

http://jakarta.apache.org/tomcat/articles/benchmark_summary.pdf

if you're testing pages that are 1k and smaller, than I you will need
2 or more jmeter clients running. hope that helps

peter



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?
> 
> > 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.
> 
> > 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]
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to