jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ha Pham <>
Subject Re: Separate User Processes?
Date Thu, 18 Feb 2016 19:56:22 GMT
Flavio and Alan,

Not sure if I misunderstood what Alan wants to achieve but each virtual
JMeter user has a separate thread (~process) so if you set JMeter to have 2
concurrent users, by default web server will consider those are 2 separate
users and will assign 2 different sessions UNLESS your web server was built
to assign session based on IP (rarely happen) because in that case both
users will have the same IP so will have an issue. You can verify this by
enable View Result Tree and see different JSESSIONIDs (which is the token
the server sends back to JMeter so that JMeter automatically sends it in
subsequent requests for the server to associate the server-side session to
the correct user) for different users.

1 JMeter can easily create hundreds of concurrent users with couple GB RAM.
It only uses significant memory if you enable heavy plugins e.g. View
Result Tree. Maybe I miss something but I don't really see the need to run
many JMeter scripts and each has only 1 user. The startup/shutdown process
is more expensive than adding another concurrent user to an existing JMeter
and that may affect the collected metrics.

Flavio is correct that tokens are typically cookies, however, token can
also be embedded in the response from servers.  If it's cookie, Cookie
Manager will handle it automatically for you (stores in local and sends in
future requests). If tokens are embedded in response from servers, you will
need to parse the response to retrieve tokens and send them along in future

Hope can help

-Ha Pham

On Thu, Feb 18, 2016 at 10:53 AM, Brown, Alan <> wrote:

> Flavio,
> Thank you for your response. We have multiple test machines set aside
> specifically for generating users, since that's how we did it back when we
> used HP Performance Center. Also, since we are concerned with server-side
> data moreso than client-side data, most of our test information is coming
> from the PerfMon agent plugin on the server machine. So, having multiple
> logs on the client side shouldn't trouble us too much although it will be
> rather messy.
> We'll experiment with the repeated command line method and get back to you.
> Thanks,
> Alan
> -----Original Message-----
> From: Flavio Cysne []
> Sent: Thursday, February 18, 2016 10:42 AM
> To: JMeter Users List
> Subject: Re: Separate User Processes?
> Maybe I have misunderstood your question, but remember that each Java
> process will allocate some memory and it stacks for each Java process you
> create. Unless you have a huge amount of memory at your disposal, this is
> not advisable.
> Said that, you could repeat a command line, that executes a JMeter script
> with only one user, as many times as the desired number of simulated users.
> Log files must be unique and you'll have to process them after the test to
> get a full view of all your processes.
> In any case, Tokens are commonly set as Cookie parameters and a HTTP
> Cookie Manager have to be added to your script.
> If your token is validated as a Header Parameter maybe you'll have to add
> its entry manually. Using the HTTP(S) Test Script Recorder to record all
> steps will indicate this if it adds automatically an HTTP Authorization
> Manager (I have experienced this when response header contains a Set-Token:
> clause)
> I hope I helped more then confused.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message