MoodleDocs - User contributions [en]

Load testing Moodle with JMeter

2022-01-07T17:55:25Z

Ratna:

Load testing Moodle with JMeter

2022-01-07T17:52:04Z

Ratna:

Load testing Moodle with JMeter

2022-01-07T17:35:17Z

Ratna:

Load testing Moodle with JMeter

2022-01-07T17:32:30Z

Ratna:

Talk:Load testing Moodle with JMeter

2021-08-23T06:17:28Z

Ratna: Created page with "I have stopped updating this page. The last state is as discussed in the forum https://moodle.org/mod/forum/discuss.php?d=424763. Please free to extend/correct as necessary."

I have stopped updating this page. The last state is as discussed in the forum https://moodle.org/mod/forum/discuss.php?d=424763.

Please free to extend/correct as necessary.

Load testing Moodle with JMeter

2021-08-23T06:13:03Z

Ratna:

Load testing Moodle with JMeter

2021-07-27T15:10:44Z

Ratna: Moved the content of https://docs.moodle.org/dev/JMeter#Make_JMeter_test_plan to https://docs.moodle.org/39/en/JMeter_test_plan_generator and linked here.

Load testing Moodle with JMeter

2021-07-27T10:00:58Z

Ratna: Moved https://docs.moodle.org/dev/Load_testing_Moodle_with_JMeter#Make_test_course to https://docs.moodle.org/39/en/Test_course_generator

Being the original load testing tool for servers, introduced in 1998(!), JMeter [http://jmeter.apache.org/] has always been the number one load testing resp. performance measuring tool for Moodle. Around its release 2.5, Moodle developers made the testing process vastly simpler by adding many scripts. The topic of this page are the two scripts ''Make test course'' and ''Make JMeter test plan'', both available under ''Site administration > Development''. Together with the set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison] they comprise a full set of load testing tools.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
(Moved to https://docs.moodle.org/39/en/Test_course_generator)

<h2>Make JMeter test plan</h2>
This script creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. Therefore the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with Moodle performance comparison [https://github.com/moodlehq/moodle-performance-comparison], which makes it easier to run the test plan in a specific Moodle environment, to gather information about the runs and to compare the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the line "$CFG->tool_generator_users_password = 'YOURSECRET';" to config.php of Moodle. You might want to set "$CFG->passwordpolicy = 0;" too, in case the proposed user password does not satisfy the password policy of the site. There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

This script is a part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the $CFG->tool_generator_users_password password set
- A page module instance
- A forum module instance with at least one discussion and one reply

You have to consider your server's capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp-up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 ramp-up period), S (30 users, 5 loops and 6 ramp-up period), M (100 users, 5 loops and 40 ramp-up period), L (1000 users, 6 loops and 100 ramp-up period), XL (5000 users, 6 loops and 500 ramp-up period) and XXL (1000 users, 7 loops and 800 ramp-up period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Consider that the server resources you will need to make bigger test plans will be accordingly higher.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

There is also a PHP CLI version of the script. Run it with --help to see its options:

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Short name of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Example:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line or on its graphical client on your desktop. First check if Java is installed in your client computer by opening a console and entering '
java -version'. If it doesn't return a version, first install [https://www.java.com/ Java] on your client. The instructions vary with the operating system.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==References==
* [1] [http://jmeter.apache.org/ Apache JMeter homepage]
* [2] [https://docs.moodle.org/en/Performance MoodleDocs Performance]
* [3] [https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
* [4] [https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2021-07-17T17:43:48Z

Ratna:

Being the original load testing tool for servers, introduced in 1998(!), JMeter [http://jmeter.apache.org/] has always been the number one load testing resp. performance measuring tool for Moodle. Around its release 2.5, Moodle developers made the testing process vastly simpler by adding many scripts. The topic of this page are the two scripts ''Make test course'' and ''Make JMeter test plan'', both available under ''Site administration > Development''. Together with the set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison] they comprise a full set of load testing tools.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates sample courses with many sections, files, various activities and users. These are intended to be used as standardized loads for checking the reliability and performance of various system components under load.

''Warning: Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will have to delete those courses (and wait for various cleanup runs) to release the space they consumed.''

Before making a course first you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER. Then go to ''Site administration > Development > Make test course''. You have a choice amoung the sizes XS, S, M, L, XL and XXL:

[[File:make-a-test-course.png|thumb]]

{| class="wikitable" border="1"
|-
! Size of course
! Approx. size
! No. of assignments
! No. of pages
! No. of small files
! No. of big files
! No. of sections
! No. of users
! No. of forum posts
! Approx. time to create
|-
! XS
| 10 kB
| 1
| 1
| 1
| 1
| 1
| 1
| 2
| 1 sec
|-
! S
| 10 MB
| 10
| 50
| 64
| 2
| 10
| 100
| 20
| 30 sec
|-
! M
| 100 MB
| 100
| 200
| 128
| 5
| 100
| 1,000
| 500
| 2 min
|-
! L
| 1 GB
| 500
| 1,000
| 1,024
| 10
| 500
| 10,000
| 5,000
| 30 min
|-
! XL
| 10 GB
| 1,000
| 5,000
| 16,384
| 10
| 1,000
| 50,000
| 10,000
| 2 hours
|-
! XXL
| 20 GB
| 2,000
| 10,000
| 32,768
| 10
| 2,000
| 100,000
| 20,000
| 4 hours
|}

Sample output (from a course of type M):
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

Pl. note that bigger courses take longer to be created - the biggest up to 4 hours on a decent server. Your server may run out of space or time out if it can't handle the size you selected.

<h2>Make JMeter test plan</h2>
This script creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. Therefore the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with Moodle performance comparison [https://github.com/moodlehq/moodle-performance-comparison], which makes it easier to run the test plan in a specific Moodle environment, to gather information about the runs and to compare the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the line "$CFG->tool_generator_users_password = 'YOURSECRET';" to config.php of Moodle. You might want to set "$CFG->passwordpolicy = 0;" too, in case the proposed user password does not satisfy the password policy of the site. There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

This script is a part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the $CFG->tool_generator_users_password password set
- A page module instance
- A forum module instance with at least one discussion and one reply

You have to consider your server's capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp-up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 ramp-up period), S (30 users, 5 loops and 6 ramp-up period), M (100 users, 5 loops and 40 ramp-up period), L (1000 users, 6 loops and 100 ramp-up period), XL (5000 users, 6 loops and 500 ramp-up period) and XXL (1000 users, 7 loops and 800 ramp-up period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Consider that the server resources you will need to make bigger test plans will be accordingly higher.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

There is also a PHP CLI version of the script. Run it with --help to see its options:

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Short name of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Example:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line or on its graphical client on your desktop. First check if Java is installed in your client computer by opening a console and entering '
java -version'. If it doesn't return a version, first install [https://www.java.com/ Java] on your client. The instructions vary with the operating system.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==References==
* [1] [http://jmeter.apache.org/ Apache JMeter homepage]
* [2] [https://docs.moodle.org/en/Performance MoodleDocs Performance]
* [3] [https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
* [4] [https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2021-07-17T09:15:32Z

Ratna:

Being the original server load testing tool, introduced in 1998(!), JMeter [1] has always been the number one load testing resp. performance measuring tool for Moodle. Around its release 2.5, Moodle developers made the testing process vastly simpler by adding many scripts. The topic of this page are the two scripts ''Make test course'' and ''Make JMeter test plan'', both available under ''Site administration > Development''. Together with the set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison] they comprise a full set of load testing tools.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates sample courses with many sections, files, various activities and users. These are intended to be used as standardized loads for checking the reliability and performance of various system components under load.

''Warning: Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will have to delete those courses (and wait for various cleanup runs) to release the space they consumed.''

Before making a course first you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER. Then go to ''Site administration > Development > Make test course''. You have a choice amoung the sizes XS, S, M, L, XL and XXL:

[[File:make-a-test-course.png|thumb]]

{| class="wikitable" border="1"
|-
! Size of course
! Approx. size
! No. of assignments
! No. of pages
! No. of small files
! No. of big files
! No. of sections
! No. of users
! No. of forum posts
! Time to create, estimated
! Time to create, actual*
|-
! XS
| 10 kB
| 1
| 1
| 1
| 1
| 1
| 1
| 2
| 1 sec
| 0.6 sec
|-
! S
| 10 MB
| 10
| 50
| 64
| 2
| 10
| 100
| 20
| 30 sec
| 12.1 sec
|-
! M
| 100 MB
| 100
| 200
| 128
| 5
| 100
| 1,000
| 500
| 2 min
| 2 min 0.1 sec
|-
! L
| 1 GB
| 500
| 1,000
| 1,024
| 10
| 500
| 10,000
| 5,000
| 30 min
| 22 min 36 sec
|-
! XL
| 10 GB
| 1,000
| 5,000
| 16,384
| 10
| 1,000
| 50,000
| 10,000
| 2 hours
| ?
|-
! XXL
| 20 GB
| 2,000
| 10,000
| 32,768
| 10
| 2,000
| 100,000
| 20,000
| 4 hours
| ?
|}

) In a VPS 8 vCPU, 32 GB RAM, 240 GB SSD storage
Sample output (from a course of type M):
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

Pl. note that bigger courses take longer to be created - up to 4 hours on a decent server. Your server may time out if it can't handle the size you selected.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the line "$CFG->tool_generator_users_password = 'moodle';" to config.php of Moodle. You might want to set "$CFG->passwordpolicy = 0;" too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<syntaxhighlight lang="php">
java -version</syntaxhighlight>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==References==
* [1] [http://jmeter.apache.org/ Apache JMeter homepage]
* [2] [https://docs.moodle.org/en/Performance MoodleDocs Performance]
* [3] [https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
* [4] [https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2021-07-08T19:21:35Z

Ratna:

Being the original server load testing tool, introduced in 1998(!), JMeter [1] has always been the number one load testing resp. performance measuring tool for Moodle. Around the release 2.5, Moodle developers made the testing process vastly simpler by adding many scripts. The topic of this page are the two scripts ''Make test course'' and ''Make JMeter test plan'', both available under ''Site administration > Development''. Together with the set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison] they comprise a full set of load testing tools.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates sample courses with many sections, files, various activities and also include users. These are intended to provide a standardized measure for checking the reliability and performance of various system components (such as backup and restore).

''Warning: Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.''

To create such a course first you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER. Then go to ''Site administration > Development > Make test course''. You have a choice amoung sizes XS, S, M, L, XL and XXL:

[[File:make-a-test-course.png|thumb]]

{| class="wikitable" border="1"
|-
! Size of course
! Approx. size
! No. of assignments
! No. of pages
! No. of small files
! No. of big files
! No. of sections
! No. of users
! No. of forum posts
! Approx. time to create
|-
! XS
| 10 kB
| 1
| 1
| 1
| 1
| 1
| 1
| 2
| 1 sec
|-
! S
| 10 MB
| 10
| 50
| 64
| 2
| 10
| 100
| 20
| 30 sec
|-
! M
| 100 MB
| 100
| 200
| 128
| 5
| 100
| 1,000
| 500
| 2 min
|-
! L
| 1 GB
| 500
| 1,000
| 1,024
| 10
| 500
| 10,000
| 5,000
| 30 min
|-
! XL
| 10 GB
| 1,000
| 5,000
| 16,384
| 10
| 1,000
| 50,000
| 10,000
| 2 hours
|-
! XXL
| 20 GB
| 2,000
| 10,000
| 32,768
| 10
| 2,000
| 100,000
| 20,000
| 4 hours
|}

Sample output (from a course of type M):
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

Pl. note that bigger courses take longer to be created - up to 4 hours on a decent server. Your server may time out if it can't handle the size you selected.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the line "$CFG->tool_generator_users_password = 'moodle';" to config.php of Moodle. You might want to set "$CFG->passwordpolicy = 0;" too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<code>
java -version</code>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==References==
* [1] [http://jmeter.apache.org/ Apache JMeter homepage]
* [2] [https://docs.moodle.org/en/Performance MoodleDocs Performance]
* [3] [https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
* [4] [https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2021-07-03T18:18:39Z

Ratna:

Being the original server load testing tool, introduced in 1998(!), JMeter [1] has always been the number one load testing resp. performance measuring tool for Moodle. Around the release 2.5, Moodle developers made the testing process vastly simpler by adding many scripts. The topic of this page are the two scripts ''Make test course'' and ''Make JMeter test plan'', both available under ''Site administration > Development''. Together with the set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison] they comprise a full set of load testing tools.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates sample courses with many sections, files, various activities and also include users. These are intended to provide a standardized measure for checking the reliability and performance of various system components (such as backup and restore).

''Warning: Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.''

To create such a course first you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER. Then go to ''Site administration > Development > Make test course''. You have a choice amoung sizes XS, S, M, L, XL and XXL:

[[File:make-a-test-course.png|thumb]]

{| class="wikitable" border="1"
|-
! Size of course
! Approx. size
! No. of assignments
! No. of pages
! No. of small files
! No. of big files
! No. of sections
! No. of users
! No. of forum posts
! Approx. time to create
|-
! XS
| 10 kB
| 1
| 1
| 1
| 1
| 1
| 1
| 2
| 1 sec
|-
! S
| 10 MB
| 10
| 50
| 64
| 2
| 10
| 100
| 20
| 30 sec
|-
! M
| 100 MB
| 100
| 200
| 128
| 5
| 100
| 1,000
| 500
| 2 min
|-
! L
| 1 GB
| 500
| 1,000
| 1,024
| 10
| 500
| 10,000
| 5,000
| 30 min
|-
! XL
| 10 GB
| 1,000
| 5,000
| 16,384
| 10
| 1,000
| 50,000
| 10,000
| 2 hours
|-
! XXL
| 20 GB
| 2,000
| 10,000
| 32,768
| 10
| 2,000
| 100,000
| 20,000
| 4 hours
|}

Sample output (from a course of type M):
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

Pl. note that bigger courses take longer to be created - up to 4 hours on a decent server. Your server may time out if it can't handle the size you selected.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the linke ''$CFG->tool_generator_users_password = 'moodle';' to config.php of Moodle. You might want to set '$CFG->passwordpolicy = 0;' too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<code>
java -version</code>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==References==
* [1] [http://jmeter.apache.org/ Apache JMeter homepage]
* [2] [https://docs.moodle.org/en/Performance MoodleDocs Performance]
* [3] [https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
* [4] [https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2021-07-03T07:50:36Z

Ratna:

Being the original server load testing tool, introduced in 1998(!), JMeter [1] has always been the number one load testing resp. performance measuring tool for Moodle. Around the release 2.5, Moodle developers made the testing process vastly simpler by adding many scripts. The topic of this page are the two scripts ''Make test course'' and ''Make JMeter test plan'', both available under ''Site administration > Development''. Together with the set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison] they comprise a full set of load testing tools.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates sample courses with many sections, files, various activities and also include users. These are intended to provide a standardized measure for checking the reliability and performance of various system components (such as backup and restore).

''Warning: Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.''

To create such a course first you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER. Then go to ''Site administration > Development > Make test course''. You have a choice amoung sizes XS, S, M, L, XL and XXL:

[[File:make-a-test-course.png|thumb]]

{| class="wikitable" border="1"
|-
! Size of course
! Approx. size
! No. of assignments
! No. of pages
! No. of small files
! No. of big files
! No. of sections
! No. of users
! No. of forum posts
! Approx. time to create
|-
! XS
| 10 kB
| 1
| 1
| 1
| 1
| 1
| 1
| 2
| 1 sec
|-
! S
| 10 MB
| 10
| 50
| 64
| 2
| 10
| 100
| 20
| 30 sec
|-
! M
| 100 MB
| 100
| 200
| 128
| 5
| 100
| 1,000
| 500
| 2 min
|-
! L
| 1 GB
| 500
| 1,000
| 1,024
| 10
| 500
| 10,000
| 5,000
| 30 min
|-
! XL
| 10 GB
| Assignments
| Pages
| Small files
| Big files
| Sections
| 100,000
| Forum posts
| 2 hours
|-
! XXL
| 20 GB
| Assignments
| Pages
| Small files
| Big files
| Sections
| 1,000,000
| Forum posts
| 4 hours
|}

Sample output (from a course of type M):
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

Pl. note that bigger courses take longer to be created - up to 4 hours on a decent server. Your server may time out if it can't handle the size you selected.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the linke ''$CFG->tool_generator_users_password = 'moodle';' to config.php of Moodle. You might want to set '$CFG->passwordpolicy = 0;' too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<code>
java -version</code>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==References==
* [1] [http://jmeter.apache.org/ Apache JMeter homepage]
* [2] [https://docs.moodle.org/en/Performance MoodleDocs Performance]
* [3] [https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
* [4] [https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2021-07-03T07:28:41Z

Ratna:

Being the original server load testing tool, introduced in 1998(!), [http://jmeter.apache.org/ Apache JMeter] has always been the number one load testing resp. performance measuring tool for Moodle. Around the release 2.5, Moodle made the testing process vastly simpler through two built-in scripts, ''Make test course'' and ''Make JMeter test plan'', both available under ''Site administration > Development''. Together with the set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison] they build a full set of load testing tools. This document is about using the aforementioned two built-in scripts.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates test courses that include many users, sections, files and various activities. This is intended to provide a standardized measure for checking the reliability and performance of various system components (such as backup and restore).

Warning: Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Once you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER, visit ''Site administration > Development > Make test course''. You have the choice between types XS, S, M, L, XL and XXL:

[[File:make-a-test-course.png|thumb]]

{| class="wikitable" border="1"
|-
! Size of course
! Approx. size
! No. of assignments
! No. of pages
! No. of small files
! No. of big files
! No. of sections
! No. of users
! No. of forum posts
! Approx. time to create
|-
! XS
| 10 kB
| 1
| 1
| 1
| 1
| 1
| 1
| 2
| 1 sec
|-
! S
| 10 MB
| 10
| 50
| 64
| 2
| 10
| 100
| 20
| 30 sec
|-
! M
| 100 MB
| 100
| 200
| 128
| 5
| 100
| 1,000
| 500
| 2 min
|-
! L
| 1 GB
| 500
| 1,000
| 1,024
| 10
| 500
| 10,000
| 5,000
| 30 min
|-
! XL
| 10 GB
| Assignments
| Pages
| Small files
| Big files
| Sections
| 100,000
| Forum posts
| 2 hours
|-
! XXL
| 20 GB
| Assignments
| Pages
| Small files
| Big files
| Sections
| 1,000,000
| Forum posts
| 4 hours
|}

Sample output (from a course of type M):
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

Pl. note that bigger courses take longer to be created - up to 4 hours on a decent server. Your server may time out if it can't handle the size you selected.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the linke ''$CFG->tool_generator_users_password = 'moodle';' to config.php of Moodle. You might want to set '$CFG->passwordpolicy = 0;' too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<code>
java -version</code>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==See also==
*[http://jmeter.apache.org/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2021-07-01T15:30:32Z

Ratna:

Being the original server load testing tool, introduced in 1998(!), [http://jmeter.apache.org/ Apache JMeter] has always been the number one load testing resp. performance measuring tool for Moodle. Around the release 2.5, Moodle made the testing process vastly simpler through two built-in scripts, ''Make test course'' and ''Make JMeter test plan'', both available under ''Site administration > Development''. Together with the set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison] they build a full set of load testing tools. This document is about using the aforementioned two built-in scripts.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates test courses that include many users, sections, files and various activities. This is intended to provide a standardized measure for checking the reliability and performance of various system components (such as backup and restore).

Warning: Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Once you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER, visit ''Site administration > Development > Make test course''. You have the choice between types XS, S, M, L, XL and XXL:

[[File:make-a-test-course.png|thumb]]

{| class="wikitable" border="1"
|-
! Type of course
! ~Size
! Assignments
! Pages
! Small files
! Big files
! Sections
! Users
! Forum posts
! ~time to create
|-
! XS
| 10 kB
| 1
| 1
| 1
| 1
| 1
| 1
| 2
| 1 second
|-
! S
| 10 MB
| 10
| 50
| 64
| 2
| 10
| 100
| 20
| 30 seconds
|-
! M
| 100 MB
| 100
| 200
| 128
| 5
| 100
| 1,000
| 500
| 2 minutes
|-
! L
| 1 GB
| 500
| 1,000
| 1,024
| 10
| 500
| 10,000
| 5,000
| 30 minutes
|-
! XL
| 10 GB
| Assignments
| Pages
| Small files
| Big files
| Sections
| 100,000
| Forum posts
| 2 hours
|-
! XXL
| 20 GB
| Assignments
| Pages
| Small files
| Big files
| Sections
| 1,000,000
| Forum posts
| 4 hours
|}

Sample output (from a course of type M):
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

Pl. note that the biggest course needs 4 hours to create on a decent server. Your server may time out if you try to created too big courses your server can handle.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the linke ''$CFG->tool_generator_users_password = 'moodle';' to config.php of Moodle. You might want to set '$CFG->passwordpolicy = 0;' too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<code>
java -version</code>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==See also==
*[http://jmeter.apache.org/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2021-06-29T12:45:01Z

Ratna:

Being the original server load testing tool, introduced in 1998(!), [http://jmeter.apache.org/ Apache JMeter] has always been the number one load testing resp. performance measuring tool for Moodle. Around the release 2.5, Moodle made the testing process vastly simpler through two built-in scripts, ''Make test course''' and ''Make JMeter test plan'', both under ''Site administration > Development'', augmented by a set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison]. This document is about using the aforementioned two built-in scripts.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates test courses that include many users, sections, files and various activities. This is intended to provide a standardized measure for checking the reliability and performance of various system components (such as backup and restore).

Warning: Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Once you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER, visit ''Site administration > Development > Make test course''. You have the choice between types XS, S, M, L, XL and XXL:

[[File:make-a-test-course.png|thumb]]

{| class="wikitable" border="1"
|-
! Type of course
! ~Size
! Assignments
! Pages
! Small files
! Big files
! Sections
! Users
! Forum posts
|-
! XS
| 10 kB
| 1
| 1
| 1
| 1
| 1
| 1
| 2
|-
! S
| 10 MB
| 10
| 50
| 64
| 2
| 10
| 100
| 20
|-
! M
| 100 MB
| 100
| 200
| 128
| 5
| 100
| 1,000
| 500
|-
! L
| 1 GB
| 500
| 1,000
| 1,024
| 10
| 500
| 10,000
| 5,000
|-
! XL
| 10 GB
| Assignments
| Pages
| Small files
| Big files
| Sections
| 100,000
| Forum posts
|-
! XXL
| 20 GB
| Assignments
| Pages
| Small files
| Big files
| Sections
| 1,000,000
| Forum posts
|}

Sample output:
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

Pl. note that the expected time to create the biggest course on a decent server is 4 hours. Your server may time out if you select too big courses for your server.

The final Continue will give you a view of the course thus created.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the linke ''$CFG->tool_generator_users_password = 'moodle';' to config.php of Moodle. You might want to set '$CFG->passwordpolicy = 0;' too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<code>
java -version</code>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==See also==
*[http://jmeter.apache.org/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2021-06-29T09:16:08Z

Ratna:

Being the original server load testing tool, introduced in 1998(!), [http://jmeter.apache.org/ Apache JMeter] has always been the number one load testing resp. performance measuring tool for Moodle. Around the release 2.5, Moodle made the testing process vastly simpler through two built-in scripts, ''Make test course''' and ''Make JMeter test plan'', both under ''Site administration > Development'', augmented by a set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison]. This document is about using the aforementioned two built-in scripts.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates test courses that include many users, sections, files and various activities. This is intended to provide a standardized measure for checking the reliability and performance of various system components (such as backup and restore).

Warning: Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Once you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER, visit ''Site administration > Development > Make test course''. You have the choice between types XS, S, M, L, XL and XXL:

[[File:make-a-test-course.png|thumb]]

{| class="wikitable" border="1"
|-
! Type of course
! ~Size
! Assignments
! Pages
! Small files
! Big files
! Sections
! Users
! Forum posts
|-
! XS
| 10 kB
| 1
| row 1, cell 3
|-
! S
| 10 MB
| 100
| row 2, cell 3
|-
! M
| 100 MB
| 1,000
| row 2, cell 3
|-
! L
| 1 GB
| 10,000
| row 2, cell 3
|-
! XL
| 10 GB
| 100,000
| row 2, cell 3
|-
! XXL
| 20 GB
| 1,000,000
| row 2, cell 3
|}

Sample output:
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

Pl. note that the expected time to create the biggest course on a decent server is 4 hours. Your server may time out if you select too big courses for your server.

The final Continue will give you a view of the course thus created.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the linke ''$CFG->tool_generator_users_password = 'moodle';' to config.php of Moodle. You might want to set '$CFG->passwordpolicy = 0;' too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<code>
java -version</code>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==See also==
*[http://jmeter.apache.org/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2021-06-29T09:05:56Z

Ratna:

Being the original server load testing tool, introduced in 1998(!), [http://jmeter.apache.org/ Apache JMeter] has always been the number one load testing resp. performance measuring tool for Moodle. Around the release 2.5, Moodle made the testing process vastly simpler through two built-in scripts, ''Make test course''' and ''Make JMeter test plan'', both under ''Site administration > Development'', augmented by a set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison]. This document is about using the aforementioned two built-in scripts.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates test courses that include many users, sections, files and various activities. This is intended to provide a standardized measure for checking the reliability and performance of various system components (such as backup and restore).

Warning: Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Once you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER, visit ''Site administration > Development > Make test course''.
[[File:make-a-test-course.png|thumb]]

You have the choice between types XS, S, M, L, XL and XXL:

{| class="wikitable" border="1"
|-
! Type of course
! Size
! users
! sections
|-
! XS
| ~10 kB
| 1
| row 1, cell 3
|-
! S
| ~10 MB
| 100
| row 2, cell 3
|-
! M
| ~100 MB
| 1,000
| row 2, cell 3
|-
! L
| ~1 GB
| 10,000
| row 2, cell 3
|-
! XL
| ~10 GB
| 100,000
| row 2, cell 3
|-
! XXL
| ~20 GB
| 1,000,000
| row 2, cell 3
|}

Sample output:
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

The final Continue will give you a view of the course thus created.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the linke ''$CFG->tool_generator_users_password = 'moodle';' to config.php of Moodle. You might want to set '$CFG->passwordpolicy = 0;' too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<code>
java -version</code>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==See also==
*[http://jmeter.apache.org/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

File:make-a-test-course.png

2021-06-29T08:55:03Z

Ratna: Make a test course, choice for its size

Make a test course, choice for its size

Load testing Moodle with JMeter

2021-06-29T08:52:26Z

Ratna:

Being the original server load testing tool, introduced in 1998(!), [http://jmeter.apache.org/ Apache JMeter] has always been the number one load testing resp. performance measuring tool for Moodle. Around the release 2.5, Moodle made the testing process vastly simpler through two built-in scripts, ''Make test course''' and ''Make JMeter test plan'', both under ''Site administration > Development'', augmented by a set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison]. This document is about using the aforementioned two built-in scripts.

Warning: Do not run these scripts on a production system! These scripts generate large amounts of artificial data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates test courses that include many users, sections, files and various activities. This is intended to provide a standardized measure for checking the reliability and performance of various system components (such as backup and restore).

Warning: Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Once you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER, visit ''Site administration > Development > Make test course''. You have the choice between XS (~10 KB; create in ~1 second), S (~10 KB, create in ~30 seconds), M (~100 KB, create in ~2 minutes), L (~1 GB, create in ~30 minutes), XL (~10 GB, create in ~2 hours) and XXL (~20 GB, created in ~4 hours).

{| class="wikitable" border="1"
|-
! Size of course
! users
! sections
|-
! XS
| 1
| row 1, cell 3
|-
! S
| 100
| row 2, cell 3
|-
! M
| 1,000
| row 2, cell 3
|-
! L
| 10,000
| row 2, cell 3
|-
! XL
| 100,000
| row 2, cell 3
|-
! XXL
| 1,000,000
| row 2, cell 3
|}

Sample output:
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

The final Continue will give you a view of the course thus created.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the linke ''$CFG->tool_generator_users_password = 'moodle';' to config.php of Moodle. You might want to set '$CFG->passwordpolicy = 0;' too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<code>
java -version</code>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==See also==
*[http://jmeter.apache.org/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2021-06-25T20:44:37Z

Ratna:

This article is a stub until we collect enough information about the developments since [https://docs.moodle.org/dev/index.php?title=JMeter&oldid=35771 previous update in 2012]. All improvements are welcome!

You can also add your comments to the [https://docs.moodle.org/dev/index.php?title=Talk:JMeter&action=edit&redlink=1 discussion page] or to the the [https://moodle.org/mod/forum/discuss.php?d=395002 discussion in the General developer forum].

<hr/ >
The [http://jmeter.apache.org/ Apache JMeter] has always been the most common load testing resp. performance measuring tool in the Moodle community. Since around release 2.5, Moodle makes the process of load testing with JMeter vastly simpler through two built-in scripts, ''Make test course''' and ''Make JMeter test plan'', both under ''Site administration > Development'', augmented by a set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison]. This document is about using the two built-in scripts with JMeter.

Warning: Do not run these scripts on a production system! These scripts generate data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates standard test courses that include many sections, activities, and files. This is intended to provide a standardized measure for checking the reliability and performance of various system components (such as backup and restore). This test is important because there have been many cases previously where, faced with real-life use cases (e.g. a course with 1,000 activities), the system does not work.

Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Once you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER, visit ''Site administration > Development > Make test course''. You have the choice between XS (~10 KB; create in ~1 second), S (~10 KB, create in ~30 secends), M (~100 KB, create in ~2 minutes), L (~1 GB, create in ~30 minutes), XL (~10 GB, create in ~2 hours) and XXL (~20 GB, created in ~4 hours).

Output:
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

The final Continue will give you a view of the course thus created.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the linke ''$CFG->tool_generator_users_password = 'moodle';' to config.php of Moodle. You might want to set '$CFG->passwordpolicy = 0;' too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<code>
java -version</code>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==See also==
*[http://jmeter.apache.org/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2020-12-08T18:17:20Z

Ratna:

This article is a stub until we collect enough information about the developments since [https://docs.moodle.org/dev/index.php?title=JMeter&oldid=35771 previous update in 2012]. All improvements are welcome!

You can also add your comments to the [https://docs.moodle.org/dev/index.php?title=Talk:JMeter&action=edit&redlink=1 discussion page] or to the the [https://moodle.org/mod/forum/discuss.php?d=395002 discussion in the General developer forum].

<hr/ >
The [http://jmeter.apache.org/ Apache JMeter] has always been the most common load testing resp. performance measuring tool in the Moodle community. Since around release 2.5, Moodle makes the process of load testing with JMeter vastly simpler through two built-in scripts, ''Make test course''' and ''Make JMeter test plan'', both under ''Site administration > Development'', augmented by a set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison]. This document is about using the two built-in scripts with JMeter.

Warning: Do not run these scripts on a production system! These scripts generate data and load the server to its limit and beyond, making it to bloat and become non-responsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates standard test courses that include many sections, activities, and files. This is intended to provide a standardized measure for checking the reliability and performance of various system components (such as backup and restore). This test is important because there have been many cases previously where, faced with real-life use cases (e.g. a course with 1,000 activities), the system does not work.

Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Once you have set the debugging level under ''Site administration > Development > Debugging'' to DEVELOPER, visit ''Site administration > Development > Make test course''. You have the choice between XS (~10 KB; create in ~1 second), S (~10 KB, create in ~30 secends), M (~100 KB, create in ~2 minutes), L (~1 GB, create in ~30 minutes), XL (~10 GB, create in ~2 hours) and XXL (~20 GB, created in ~4 hours).

Output:
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

The final Continue will give you a view of the course thus created.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. Here too it is necessary to set ''Site administration > Development > Debugging'' to DEVELOPER. Also note that, unlike making the test course, this is a single script. To the PHP max_execution_time need to be at least as long as the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set the same password for all the test users by adding the linke ''$CFG->tool_generator_users_password = 'moodle';' to config.php of Moodle. You might want to set '$CFG->passwordpolicy = 0;' too in case the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit ''Site administration > Development > Make JMeter test plan''. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above. Also ''Update course users password'' should be ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
JMeter is a Java application so it can run on Windows, Mac, or Linux. It can be run on the command line on a server but you should also install a graphical user interface version on your desktop. You can check if Java is installed by opening a console and entering:
<code>
java -version</code>
If it doesn't return a version, go to the [https://www.java.com/ Java] site and install.

To install JMeter go to the [http://jmeter.apache.org/download_jmeter.cgi JMeter page], download the zip and unzip it to the directory of your choice.

To run JMeter. open the /bin subdirectory and use either jmeter.bat on Windows or ./jmeter on Linux. This will open the JMeter GUI.

First step is to go to File -> Open and select the testplan.jmx file. This will open a tree on the left hand side of JMeter.
Open the Warm-up site -> Default site request and enter the protocol (http or https) and Server name or IP. Then go to CSV Users Data and locate your users.csv file under Filename. <b>Repeat </b> this for Moodle Test.

Right mouse click on the Test Plan, then Add -> Listener. I choose Aggregate Report so I can follow the run as it happens. Save the changes in your test plan and run it.

==See also==
*[http://jmeter.apache.org/jmeter/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2020-05-23T08:41:57Z

Ratna:

This article is a stub until we collect enough information about the developments since [https://docs.moodle.org/dev/index.php?title=JMeter&oldid=35771 previous update in 2012]. All improvements are welcome!

You can also add your comments to the [https://docs.moodle.org/dev/index.php?title=Talk:JMeter&action=edit&redlink=1 discussion page] or to the the [https://moodle.org/mod/forum/discuss.php?d=395002 discussion in the General developer forum].

<hr/ >
The [http://jmeter.apache.org/ Apache JMeter] has always been the most common load testing resp. performance measuring tool in the Moodle community. Since around release 2.5, Moodle makes the process of load testing with JMeter vastly simpler through two built-in scripts, ""Make test course''' and '''Make JMeter test plan''', both under Site administration > Development, augmented by a set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison]. This document is about using the two built-in scripts with JMeter.

Warning: '''Do not run these scripts on a production system!''' These scripts generate data and load the server to its limit and beyond, making it to bloat and become non-reponsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates standard test courses that include many sections, activities, and files. This is intended to provide a standardised measure for checking the reliability and performance of various system components (such as backup and restore). This test is important because there have been many cases previously where, faced with real-life use cases (e.g. a course with 1,000 activities), the system does not work.

Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Once you have set the debugging level Site administration > Development > Debugging: Debug messages = DEVELOPER: extra Moodle debug messages for developers, visit Site administration > Development > Make test course. You have the choice between XS (~10 KB; create in ~1 second), S (~10 KB, create in ~30 secends), M (~100 KB, create in ~2 minutes), L (~1 GB, create in ~30 minutes), XL (~10 GB, create in ~2 hours) and XXL (~20 GB, created in ~4 hours).

Output:
Creating course
Creating [Course name]
Creating assignments (100): . . . . . . . . . . . . done (12.7s)
Creating pages (200): . . done (1.5s)
Creating small files (128): done (0.4s)
Creating big files (5): . done (1.3s)
Checking user accounts (1000)
Creating user accounts (1 - 1000): . . . . . . . . done (8.7s)
Enrolling users into course (1000): . . . . . . done (5.7s)
Creating forum (500 posts): . . done (1.7s)
Course completed (32.2s)

The final Continue will give you a view of the course thus created.

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file.

This test plan is designed to work along with [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison], which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set a password for the course users in config.php (e.g. $CFG->tool_generator_users_password = 'moodle';). You might want to set $CFG->passwordpolicy = 0; in your config.php if the proposed user password conflicts with the password policy of the site.

There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
- A page module instance
- A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Visit Site administration > Development > Make JMeter test plan. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above.
Update course users password: ticked.

Once successful you can download a test plan [[File:testplan_timestamp.jmx|testplan_timestamp.jmx]] and a users file [[File:users_timestamp.csv|users_timestamp.csv]]

$ php admin/tool/generator/cli/maketestplan.php --help
Options:
-h, --help Print out this help
--shortname Shortname of the test plan's target course (required)
--size Size of the test plan to create XS, S, M, L, XL, or XXL (required)
--bypasscheck Bypasses the developer-mode check (be careful!)
--updateuserspassword Updates the target course users password according to $CFG->tool_generator_users_password

* XS (1 Nutzter, 5 Schleifen und 1 Steigerungsrate)
* S (30 Nutzter, 5 Schleifen und 6 Steigerungsrate)
* M (100 Nutzter, 5 Schleifen und 40 Steigerungsrate)
* L (1000 Nutzter, 6 Schleifen und 100 Steigerungsrate)
* XL (5000 Nutzter, 6 Schleifen und 500 Steigerungsrate)
* XXL (10000 Nutzter, 7 Schleifen und 800 Steigerungsrate)

Consider that, the server resources you will need to run the test plan will be higher as the test plan size is higher.

Example from Moodle root directory:
$ sudo -u www-data /usr/bin/php admin/tool/generator/cli/maketestplan.php --shortname="testcourse_12" --size=S

<h2>Running the test plan on JMeter</h2>
(to be filled)

==See also==
*[http://jmeter.apache.org/jmeter/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2020-05-18T22:03:46Z

Ratna:

Load testing Moodle with JMeter

2020-03-03T20:55:34Z

Ratna:

This article is a stub until we collect enough information about the developments since [https://docs.moodle.org/dev/index.php?title=JMeter&oldid=35771 previous update in 2012]. All improvements are welcome!

You can also add your comments to the [https://docs.moodle.org/dev/index.php?title=Talk:JMeter&action=edit&redlink=1 discussion page] or to the the [https://moodle.org/mod/forum/discuss.php?d=395002 discussion in the General developer forum].

<hr/ >
The [http://jmeter.apache.org/ Apache JMeter] has always been the most common load testing resp. performance measuring tool in the Moodle community. Since around release 2.5, Moodle makes the process of load testing with JMeter vastly simpler through two built-in scripts, (Site administration > Development >) ""Make test course''' and (dito >) '''Make JMeter test plan''', augmented by a set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison]. This document is about the two built-in scripts and JMeter.

Warning: '''Do not run these scripts on a production system!'''

These scripts generate data and load the server to its limit and beyond, making it to bloat and become nonreponsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates standard test courses that include many sections, activities, and files. This is intended to provide a standardised measure for checking the reliability and performance of various system components (such as backup and restore). This test is important because there have been many cases previously where, faced with real-life use cases (e.g. a course with 1,000 activities), the system does not work. Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Do not use this feature on a live system. Use only on a developer server. (To avoid accidental use, this feature is disabled unless you have also selected DEVELOPER debugging level.)

Once you have set the debugging level Site administration > Development > Debugging: Debug messages = DEVELOPER: extra Moodle debug messages for developers, visit Site administration > Development > Make test course. You have the choice between XS (~10 KB; create in ~1 second), S (~10 KB, create in ~30 secends), M (~100 KB, create in ~2 minutes), L (~1 GB, create in ~30 minutes), XL (~10 GB, create in ~2 hours) and XXL (~20 GB, created in ~4 hours).

Output:
Creating course
Creating course [short name]
Creating assignments (1): done (0.1s)
Creating pages (1): done (0s)
Creating small files (1): done (0s)
Creating big files (1): done (0s)
Checking user accounts (1)
Creating user accounts (1 - 1): done (0s)
Enrolling users into course (1): done (0s)
Creating forum (2 posts): done (0s)
Course completed (0.3s)

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. This test plan is designed to work along with https://github.com/moodlehq/moodle-performance-comparison, which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set a password for the course users in config.php (e.g. $CFG->tool_generator_users_password = 'moodle';). There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:

Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
A page module instance
A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Do not run the test plan on a live system. This feature only creates the files to feed JMeter so is not dangerous by itself, but you should NEVER run this test plan in a production site.

Visit Site administration > Development > Make JMeter test plan. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above.
Update course users password: ticked.

Now set $CFG->tool_generator_users_password in config.php to generate the test plan. Once successful you can download a test plan (jmx file) [[File:users_timestamp.csv|users_timestamp.csv]] and a users file (csv)
<h2>Running the test plan on JMeter</h2>
(to be filled)

==See also==
*[http://jmeter.apache.org/jmeter/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2020-02-19T15:25:18Z

Ratna:

This article is a stub until we collect enough information about the developments since [https://docs.moodle.org/dev/index.php?title=JMeter&oldid=35771 previous update in 2012]. All improvements are welcome!

You can also add your comments to the [https://docs.moodle.org/dev/index.php?title=Talk:JMeter&action=edit&redlink=1 discussion page] or to the the [https://moodle.org/mod/forum/discuss.php?d=395002 discussion in the General developer forum].

<hr/ >
The [http://jmeter.apache.org/ Apache JMeter] has always been the most common load testing resp. performance measuring tool in the Moodle community. Since around release 2.5, Moodle makes the process of load testing with JMeter vastly simpler through two built-in scripts '''Make test course''' (Site administration > Development > Make test course) and '''Make JMeter test plan''' (dito > Make JMeter test plan) augmented by a set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison]. This document is about the two built-in scripts and JMeter.

Warning: '''Do not run these scripts on a production system!'''

These scripts generate data and load the server to its limit and beyond, making it to bloat and become nonreponsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates standard test courses that include many sections, activities, and files. This is intended to provide a standardised measure for checking the reliability and performance of various system components (such as backup and restore). This test is important because there have been many cases previously where, faced with real-life use cases (e.g. a course with 1,000 activities), the system does not work. Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Do not use this feature on a live system. Use only on a developer server. (To avoid accidental use, this feature is disabled unless you have also selected DEVELOPER debugging level.)

Once you have set the debugging level Site administration > Development > Debugging: Debug messages = DEVELOPER: extra Moodle debug messages for developers, visit Site administration > Development > Make test course. You have the choice between XS (~10 KB; create in ~1 second), S (~10 KB, create in ~30 secends), M (~100 KB, create in ~2 minutes), L (~1 GB, create in ~30 minutes), XL (~10 GB, create in ~2 hours) and XXL (~20 GB, created in ~4 hours).

Output:
Creating course
Creating course [short name]
Creating assignments (1): done (0.1s)
Creating pages (1): done (0s)
Creating small files (1): done (0s)
Creating big files (1): done (0s)
Checking user accounts (1)
Creating user accounts (1 - 1): done (0s)
Enrolling users into course (1): done (0s)
Creating forum (2 posts): done (0s)
Course completed (0.3s)

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. This test plan is designed to work along with https://github.com/moodlehq/moodle-performance-comparison, which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set a password for the course users in config.php (e.g. $CFG->tool_generator_users_password = 'moodle';). There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:

Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
A page module instance
A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Do not run the test plan on a live system. This feature only creates the files to feed JMeter so is not dangerous by itself, but you should NEVER run this test plan in a production site.

Visit Site administration > Development > Make JMeter test plan. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above.
Update course users password: ticked.

Now set $CFG->tool_generator_users_password in config.php to generate the test plan. Once successful you can download a test plan (jmx file) [[File:users_timestamp.csv|users_timestamp.csv]] and a users file (csv)
<h2>Running the test plan on JMeter</h2>
(to be filled)

==See also==
*[http://jmeter.apache.org/jmeter/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2020-02-18T15:31:34Z

Ratna:

This article is a stub until we collect enough information about the developments since [https://docs.moodle.org/dev/index.php?title=JMeter&oldid=35771 previous update in 2012]. All improvements are welcome!

You can also add your comments to the [https://docs.moodle.org/dev/index.php?title=Talk:JMeter&action=edit&redlink=1 discussion page] or to the the [https://moodle.org/mod/forum/discuss.php?d=395002 discussion in the General developer forum].

<hr/ >
The [http://jmeter.apache.org/ Apache JMeter] has always been the most common load testing resp. performance measuring tool in the Moodle community. Since around release 2.5, Moodle makes the process of load testing with JMeter vastly simpler through two built-in scripts '''Make test course''' (Site administration > Development > Make test course) and '''Make JMeter test plan''' (dito > Make JMeter test plan) augmented by a set of add-ons [https://github.com/moodlehq/moodle-performance-comparison Moodle performance comparison]. This document is about the two built-in scripts and JMeter.

Warning: '''Do not run these scripts on a production system!'''

These scripts generate data and load the server to its limit and beyond, making it to bloat and become nonreponsive. Don't even run them on a separate Moodle instance in the production server: their effect on the DBMS is undocumented.

<h2>Make test course</h2>
This tool creates standard test courses that include many sections, activities, and files. This is intended to provide a standardised measure for checking the reliability and performance of various system components (such as backup and restore). This test is important because there have been many cases previously where, faced with real-life use cases (e.g. a course with 1,000 activities), the system does not work. Courses created using this feature can occupy a large amount of database and filesystem space (tens of gigabytes). You will need to delete the courses (and wait for various cleanup runs) to release this space again.

Do not use this feature on a live system. Use only on a developer server. (To avoid accidental use, this feature is disabled unless you have also selected DEVELOPER debugging level.)

Once you have set the debugging level Site administration > Development > Debugging: Debug messages = DEVELOPER: extra Moodle debug messages for developers, visit Site administration > Development > Make test course. You have the choice between XS (~10 KB; create in ~1 second), S (~10 KB, create in ~30 secends), M (~100 KB, create in ~2 minutes), L (~1 GB, create in ~30 minutes), XL (~10 GB, create in ~2 hours) and XXL (~20 GB, created in ~4 hours).

Output:
Creating course
Creating course [short name]
Creating assignments (1): done (0.1s)
Creating pages (1): done (0s)
Creating small files (1): done (0s)
Creating big files (1): done (0s)
Checking user accounts (1)
Creating user accounts (1 - 1): done (0s)
Enrolling users into course (1): done (0s)
Creating forum (2 posts): done (0s)
Course completed (0.3s)

<h2>Make JMeter test plan</h2>
This tool creates a JMeter test plan file along with the user credentials file. This test plan is designed to work along with https://github.com/moodlehq/moodle-performance-comparison, which makes easier to run the test plan in a specific Moodle environment, gathers information about the runs and compares the results, so you will need to download it and use it's test_runner.sh script or follow the installation and usage instructions.

You need to set a password for the course users in config.php (e.g. $CFG->tool_generator_users_password = 'moodle';). There is no default value for this password to prevent unintended usages of the tool. You need to use the update passwords option in case your course users have other passwords or they were generated by tool_generator but without setting a $CFG->tool_generator_users_password value.

It is part of tool_generator so it works well with the courses generated by the courses and the site generators, it can also be used with any course that contains, at least:

Enough enrolled users (depends on the test plan size you select) with the password reset to 'moodle'
A page module instance
A forum module instance with at least one discussion and one reply

You might want to consider your servers capacity when running large test plans as the amount to load generated by JMeter can be specially big. The ramp up period has been adjusted according to the number of threads (users) to reduce this kind of issues but the load is still huge.

Do not run the test plan on a live system. This feature only creates the files to feed JMeter so is not dangerous by itself, but you should NEVER run this test plan in a production site.

Visit Site administration > Development > Make JMeter test plan. Under Size of course your have six possibilities: XS (1 user, 5 loops and 1 rampup period), S (30 users, 5 loops and 6 rampup period), M (100 users, 5 loops and 40 rampup period), L (1000 users, 6 loops and 100 rampup period), XL (5000 users, 6 loops and 500 rampup period) and XXL (1000 users, 7 loops and 800 rampup period). As target course select one of the courses created above.
Update course users password: ticked.

Now set $CFG->tool_generator_users_password in config.php to generate the test plan. Once successfull you can download a test plan (jmx file) [[File:users_timestamp.csv|thumb]] and a users file (csv)
<h2>Running the test plan on JMeter</h2>
(to be filled)

==See also==
*[http://jmeter.apache.org/jmeter/ Apache JMeter homepage]
*[https://moodle.org/mod/forum/discuss.php?d=377231 Jmeter or loading script/app to simulate concurrent users takng quizzes] (October 2018)
*[https://moodle.org/mod/forum/discuss.php?d=368620 Has anyone successfully run a jmeter test with 1000 users?] (April 2018)

[[Category:Developer tools]]

Load testing Moodle with JMeter

2020-02-18T15:15:34Z

Ratna:

Load testing Moodle with JMeter

2019-12-29T09:34:22Z

Ratna:

Load testing Moodle with JMeter

2019-12-28T16:20:31Z

Ratna:

Load testing Moodle with JMeter

2019-12-28T10:36:53Z

Ratna:

User talk:Visvanath Ratnaweera

2009-10-10T08:21:25Z

Ratna: /* new section */ new section

2009-10-10 Talk back viz

== new section ==

xxxx

User talk:Visvanath Ratnaweera

2009-10-10T08:20:04Z

Ratna: New page: 2009-10-10 Talk back viz

2009-10-10 Talk back viz