New answers tagged

0

One of the main benefits to running Selenium Grid is you can run lots of parallel tests and in different combinations of environments. Even if you run only one browser + operating system you might still benefit from the fact these are hermetic systems, isolated from each other. Therefore one browser failure won't cause the other tests to fail. Although, ...


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


0

You could design this scenario using a "Recorder". First, you need to record your script and you have to add "HTTP Cookie Manager" in your script manually after recording is done.Enable "Clear Cache Each Iteration". This will render your page resource every time it sends a request and clear the cache before a new incoming request. And to manage throughput ...


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!!


0

That is easier said than done. Will you be spinning up a new virtual user for each IP address or session ID encountered? How will you handle the substitution of dynamic elements present in the log which are no longer appropriate for execution? What about elements which are cached but which do not show up in the log? You are much better off to take the ...


0

Although Constant Throughput Timer accepts value in Requests/min and you are saying that you will use 120/sec, so you will have to provide a value of 7200 in Constant Throughput Timer to achieve 120/sec. Assuming there is only one request (sampler) in your Thread group and you are using the setting "All Active Threads" in Constant Throughput Timer. Then by ...


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


0

It depends on what "server" you're running. If you're lucky enough to have your application running on Apache Tomcat you will be able to use Access Log Sampler which comes with JMeter. If not - there is still an option to parse your log with Beanshell PreProcessor and change HTTP Request parameters on the fly. See Stop Making Assumptions! Learn How to ...


0

Constant Throughput Timer can only pause the threads to reach specified "Target Throughput" value so make sure you provide enough virtual users (threads) to generate desired "requests per minute" value. See How to use JMeter's Throughput Constant Timer guide for more information.


0

As far as I know, it doesn't matter which type of Thread group you are using with Constant Throughput timer, at the end of the test in the results, you will get your desired Throughput which you mentioned in Constant Throughput Timer i.e. if you have mentioned 1200/min in Constant Throughput Timer with "Calculate Throughput based on" value as "All active ...


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


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


-1

1 concurrent user. 5 ramup second / 20 thread = 0.25. every user starts action at the interval of 0.25 second


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


0

As per your configuration, each thread(user) will start their action after 20/100 =0.2 seconds. i.e. after first thread has initiated, second thread will start after 0.2 seconds. If you want to verify the same from Jmeter, on the top right corner threads are shown once you start the action.


0

This might be because some of application requests are taking too long to execute, holding the application server’s threads busy, and not allowing the resources to be used by incoming requests. Try the running the test with 4000 concurrent users, then 6000 users and so on. Check at number of request you are getting this error.You must verify Apache ...


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.


0

JMeter provides a way to perform distributed testing. This comes in the form of a master-slave setup. In this mode, there is a machine known as a master, which controls a number of client machines (JMeter instances) known as slaves. This approach has some benefits, including managing multiple JMeter instances remotely from the master node, automatically ...


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


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


3

Since you're dealing with client-server architecture, you're also dealing with network latency, spin-up times, disk latency on the server and the client system, potential I/O bottlenecks (and the testing tool itself is not exactly lightweight in I/O terms), network traffic, and numerous other factors. Your first priority should be to limit/minimize as many ...


0

Assuming you are using Windows you can define the CPU settings under Power Options in the Control Panel Control Panel\All Control Panel Items\Power Options Select the plan you require and "Edit Plan Settings" then select "Change advanced power settings" (I would suggest you set up a separate plan for each scenario you plan to use to make it easy to switch ...



Top 50 recent answers are included