Caching: Difference between revisions
From MoodleDocs
Helen Foster (talk | contribs) (brief intro) |
Helen Foster (talk | contribs) (useful links thanks to Nadav Kavalerchik) |
||
| Line 3: | Line 3: | ||
Moodle 2.4 saw the implementation of MUC Stage 1: Implement some core caching architecture. | Moodle 2.4 saw the implementation of MUC Stage 1: Implement some core caching architecture. | ||
Two links, that might be useful to anyone considering testing the new features on their own servers: | |||
* [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?] | |||
* [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm] | |||
==See also== | ==See also== | ||
Revision as of 10:53, 4 December 2012
A cache is a collection of data that is kept on hand and made readily available in order to avoid costly fetching and moulding upon every request.
Moodle 2.4 saw the implementation of MUC Stage 1: Implement some core caching architecture.
Two links, that might be useful to anyone considering testing the new features on their own servers:
- Moodle performance testing: how much more horsepower do each new versions of Moodle require?
- How to load test your Moodle server using Loadstorm
See also
- Using Moodle MUC is here, now what? forum discussion
Developer documentation:
