Load testing Moodle with JMeter: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 5: | Line 5: | ||
<hr/ > | <hr/ > | ||
The | 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!''' | Warning: '''Do not run these scripts on a production system!''' | ||
These | 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> | <h2>Make test course</h2> | ||
Revision as of 09:34, 29 December 2019
This article is a stub until we collect enough information about the developments since previous update in 2012. All improvements are welcome!
You can also add your comments to the discussion page or to the the discussion in the General developer forum.
The 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 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.
Make test course
(to be filled)
Make JMeter test plan
(to be filled)
Running the test plan on JMeter
(to be filled)
