Load testing Moodle with JMeter: Difference between revisions
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
<h2>Running the test plan on JMeter</h2> | <h2>Running the test plan on JMeter</h2> | ||
(to be filled) | (to be filled) | ||
==See also== | ==See also== | ||
*[http://jmeter.apache.org/jmeter/ Apache JMeter homepage] | *[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]] | [[Category:Developer tools]] | ||
Revision as of 16:20, 28 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 Apace JMeter has always been the most common load testing resp. performance measurement tool for Moodle. Since release 2.5, Moodle makes the process vastly simpler through two built-in scripts Make test course (Site administration > Development > Make test course) and Make JMeter test plan (Site administration > Development > Make JMeter test plan) augmented by the add-ons Moodle performance comparison. This document is about the two built-in scripts.
Warning: Do not run these scripts on a production system!
These tests load the server to its limits and beyond, making it nonreponsive. Even if you can afford down-times don't run them on a separate Moodle instance on 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)
