Hot answers tagged

4

To avoid mutual interference it is much better to run JMeter and Application Under Test on different hosts. Theoretically you can have them on same machine but results won't be reliable. Load Testing is not only about getting main metrics and KPIs like response time, transactions per second, throughput, etc. - a lot of other information needs to be ...


3

Network is the highest cost resource in terms of adding to response time. When you run on the same server as the web server you are processing requests and responses across the system bus of the system, which is order of magnitude faster than the network where the clients will be collected. You are also shaping the performance curve of the server to ...


3

Answer In Short Strictly Recommended Method: Execute JMeter Scripts on remote server. Reason: JMeter use huge memory which affects the performance of machine, hence executing JMeter script on same server will generate the false report.


3

The second one is the only way. It is strictly recommended that you do not run a JMeter test from a server where you already have the application installed which has to be tested.Jmeter test consumes a huge memory resource from server or machine. So if you have JMeter & the application to be tested on the same server, you can't expect to have accurate ...


2

This is a network constraint over which you may not have any control. Do you know after what time you get this error? You could play with Timeouts section on HTTP Request Sample and keep it higher than the time which causes timeout error.


2

I don't know why you need to run multiple instances of Jmeter from single machine. But Yes, you can run multiple instances of JMeter from single machine without any major issue, the only limitation will be with the memory used by JMeter as if you ran too many instances or few instances using too much memory then you may ran out of memory and JMeter execution ...


2

It depends. JMeter acts as follows: JMeter starts defined number of threads during ramp-up period Threads start executing samplers upside down (or according to Logic Controllers) When thread doesn't have any more samplers to execute or loops to iterate - it's being shut down So if your test is short enough you may easily run into a situation when 1st ...


2

Answer is 1500. During hold time only 1500 requests will be kept alive. It depends on many factors and one of the factor is whether you used "Cookie Manager" in your scripts. If "Clear cookie each iteration" checkbox is checked then every session or cookies will be cleared after each iteration. So At the hold time only 1500 requests will be alive ...


2

That depends on how you use JMeter. The tool was originally designed for performance testing. If you run JMeter on the same machine as your application, your application may run slower or encounter other resource contention issues compared to running JMeter on a different machine. On the other hand, some people use JMeter for functional testing. For that ...


1

To control your throughput per minute you have to use either Constant Throughput Timer or Throughput Shaping Timer. But I would recommend you to use Constant Throughput Timer (Since I haven't use Throughput Shaping Timer). Actually, Constant Throughput Timer can only pause the threads to reach specified "Target Throughput" value so make sure you provide ...


1

You can use "jp@gc - Active Threads Over Time". For Details: See Here--> Active Threads Over Time Hope, this will satisfy your query. Thanks!!


1

That depends on how your system defines a login session. Typically it is the server, not the client, that decides when a login session is over. You need to figure out (or ask a developer to describe) the session lifecycle for your system.


1

If you have 100 Threads in thread group and Ramp up time as 20, these 100 threads aren't concurrent. To maintain concurrency for 100 threads you have to use either loop counts or Durations (Scheduler in Thread Group). You may try with the "Ultimate Thread Group" (JMeter plugins) instead of only "Thread group". To check this, you can use "Active Threads Over ...


1

set ramp up time to zero to start all the thread at same time. difference in starting time between threads = Ramp up time/ no of threads. If you have ramp up time = 20 and no of threads = 100 then each thread with start with time gap of 0.2 (20/100) sec from previous thread


1

While loop condition can have 3 types of value: • Blank : The loop will exit only when at least one of the test element fails. if the failing sample is not the last sample under while controller, then remaining test element would be executed and then loop is exited • LAST : loop will exit only if the last test element under while controller fails. ...



Only top voted, non community-wiki answers of a minimum length are eligible