jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject Re: What is the relationship between JVM XMX and XMS in jmeter and the number of concurrent users
Date Mon, 28 Jan 2019 09:04:53 GMT
JMeter is a normal Java application hence you should treat it as any other
Java application in terms of  performance tuning

There is no "silver bullet" instruction. Neither anyone can tell how many
users you will be able to simulate for this or that test as "it depends".
Mainly it depends on:

1. Nature of your test (what the test is doing, request and response size,
number of  Preprocessors
,  Postprocessors
,  Assertions
<>  , etc).
Remember that any test element has its cost and try to limit their usage to
absolute viable minimum. 

2. It is not possible to provide "recommended" minimum and maximum heap
values as it also depends on how JMeter copes with the load. You can see
what's going on using  JVisualVM
tool. First of all, maximum heap should be big enough in order to fit in
JMeter, all thread variables, requests and responses data for all the
threads, if the data will not fit into heap - you will get 
java.lang.OutOfMemoryError: Java heap space

. Going forward if JVisualVM shows that Java spends too much time doing GC -
you might want to increase heap size and vice versa, you might want to
decrease heap usage to give resources to other processes. 

3. Remember that any heap manipulation should be followed by the amendment
of other parameters like  MaxMetaSpaceSize

So start with default settings and ensure that:

1. Java uses machine resources efficiently, i.e. you don't have too many
spare RAM and CPU
2. System isn't overloaded,  i.e. there is no lack of CPU or RAM
3. JVM doesn't spend too much time doing GC

If you performed all the optimisations and still unable to conduct the
required load - you will have to go for  Distributed Testing

Sent from:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message