CODEWITHSUNDEEP
jmeterload-testing
Yaniv Donenfeld
Yaniv Donenfeld

Reputation: 663

Simulate millions of users with JMeter

I have a system that should be able to handle millions of users requests concurrently. In order to check how the system handles the load, I setup a cluster of JMeter servers (slaves), and one controller (client).

I have a database of all users (~10M), and I need each request sent to be from a different user.

I am wondering how I can implement such a thing in JMeter. Basically, I thought about dividing a range of users (let's say 100,000) per each slave, and then within a given slave, each request should read a new user from the local 100,000 list, and delete it. Thus, I will eventually send a request from every user.

The thing is while this idea sounds logical theoretically, I do not exactly know how to implement it using the JMeter terms. Also, I am not sure how to read from database in the test, although I could theoretically read it in advance into a text file, and have each slave contain the text file with its 100,000 users portion.

I can setup a very large cluster of machines, so scale will not be the issue here. Just how to set it all up.

Upvotes: 2

Views: 3035

Answers (2)

itaymendel
itaymendel

Reputation: 748

The best way to provide Jmeter with a list of parameters is to use a CSV file: http://jmeter.apache.org/usermanual/component_reference.html#CSV_Data_Set_Config You can configure the CSV dataset config to do make every thread use a different line in the CSV. Each engine will need to have it’s own unique CSV file, because the sharing mode does nto work between engines in distributed testing (you can try to automate this part, this can be interesting to do :) ).

This is how your script should look like:
1. Thread Group
1.1 HTTP sampler (login)
1.1.1 CSV dataset config
1.2 second http sampler
etc...

The login sampler will use the parameters loaded by from the CSV file, so for every ’login’ it will use a different line.

Distributed testing is pretty simple: http://jmeter.apache.org/usermanual/remote-test.html Keep in mind that running 100K concurrent users on a single Jmeter load engine will be hard (Jmeter consumes resources on the server, so you will need lots of CPU and memory). So you should also monitor the engines. Also 1M users will cause a lot of data that the engines will send back to the console, so you might need to start a bunch of distributed tests in parallel, and at the end aggregate the results.

Cheers,

Upvotes: 1

Zubair M Hamdani
Zubair M Hamdani

Reputation: 1733

This is can be implemented by doing the following steps:

  • Taking the user credential dump and saving it to a csv file
  • split the csv file. copy 1 file to each Jmeter slave, in the same location on all the machines e.g. "C:\Loadtest\"
  • from the controller, give the path of your csv file in "CSV Data Set Config".
  • Run the Test.

By doing the above steps, Jmeter controller will start execution of the test by pointing all the Jmeter Slave nodes to use the CSV file in the same location "C:\Loadtest\". But the trick here is that all the machine will be using different set of users.

Hope this will help.

Upvotes: 0

Related Questions