MoodleDocs - User contributions [en]

Talk:Test course generator

2021-08-23T05:55:59Z

Ratna: Created page with "I have stopped updating this page. My last state is documented in https://moodle.org/mod/forum/discuss.php?d=424763. Please free to edit/correct them. Also note that the maj..."

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

Please free to edit/correct them.

Also note that the major changes I made on 27 July 2021 https://docs.moodle.org/39/en/index.php?title=Test_course_generator&type=revision&diff=138909&oldid=133519 were done after the /39/ wiki was duplicated as /310/ (and further). So those changes do not reflect in /310/ wiki and following wikis.

Talk:JMeter test plan generator

2021-08-23T05:50:59Z

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

Please free to edit/correct them.

Also note that the major changes I made on 27 July 2021 https://docs.moodle.org/39/en/index.php?title=JMeter_test_plan_generator&type=revision&diff=138907&oldid=118517 were done after the /39/ wiki was duplicated as /310/ (and further). So those changes do not reflect in /310/ wiki and following wikis.

Test course generator

2021-07-27T20:01:49Z

Ratna:

{{Developer tools}}
If you want a sample course for load testing or reliability of a feature (where its behaviour might depend on the size of a course), you can generate standardized test courses using the generator tool at ''Administration > Site administration > Development > Make a test course''.,

''Warning: This tool is for developer use only! Courses created using this feature can occupy a large amount of database and consume disk space (tens of gigabytes). Although you can delete those courses (and wait for various cleanup runs) to release the space they consumed, this tool should not be used on a live site. For safety it is disabled unless you set Site administration > Development > Debugging: Debug messages to DEVELOPER. ''

== Using the tool ==

# First set the debugging level to DEVELOPER as mentioned in the warning above.
# If you want to set a password for all the generated users, add the line "$CFG->tool_generator_users_password = 'YOURSECRET';" to config.php of Moodle. If the password does not comply with the site security policy to set "$CFG->passwordpolicy = 0;" too.

=== GUI version ===
# Visit Administration > Site administration > Development > Make a test course. [[File:make-test-course.png]]

==== Options ====
* Size of course: You can choose amoung XS, S, M, L, XL, or XXL (required). The table below shows their difference.

Please 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.

{| 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
|}

* Course short name: The course short name (required)
* Course full name and Course summary: (optional)

==== 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)

== CLI version ==

You can run the tool from the command-line using:

php admin/tool/generator/cli/maketestcourse.php

This will show command-line options.

=== Options ===
In addition to the options in the GUI version the CLI command has the following options:

* Use a fixed dataset: Use a fixed data set instead of randomly generated data, useful for generating a standard data set
* Specify a file size limit: Limits the size of the generated files to the specified number of bytes, you may find this setting useful because depending on the size you select the courses can use too much disk space
* By pass check: Bypasses the developer-mode check
* Quiet: Do not show any output

[[es:Generador de curso de prueba]]
[[de:Testkurs-Generator]]

File:make-test-course.png

2021-07-27T19:52:21Z

Ratna:

JMeter test plan generator

2021-07-27T15:04:56Z

Ratna: Imported the content of https://docs.moodle.org/dev/JMeter#Make_JMeter_test_plan and merged.

{{Developer tools}}
This script creates a test plan file (*.jmx) along with the user credentials file (.csv) which you can either feed to JMeter to run a load test. This test plan is also 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.

''Warning: This tool is for developer use only! Courses created using this feature can occupy a large amount of database and consume disk space (tens of gigabytes). Although you can delete those courses (and wait for various cleanup runs) to release the space they consumed, this tool should not be used on a live site. For safety it is disabled unless you set Site administration > Development > Debugging: Debug messages to DEVELOPER. ''

Also note that, unlike making the [[Test course generator]], this is a single script. Therefore the PHP max_execution_time needs to be greater that the time for the whole script, which could be anything from a minute to hours depending on the size of the course you select.

== Using the tool ==

# First set the debugging level to DEVELOPER as mentioned in the warning above.
# If you want to set a password for all the generated users, add the line "$CFG->tool_generator_users_password = 'YOURSECRET';" to config.php of Moodle. If the password does not comply with the site security policy to set "$CFG->passwordpolicy = 0;" too.

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 [[Test course generator]] and the site generator. It can also be used with any course that contains, at least:
- Enough enrolled users (depends on the test plan size you select)
- 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 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.

=== GUI version ===
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]]

=== CLI version ===
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
cd /moodle/dirroot
php admin/tool/generator/cli/maketestplan.php --size=S --shortname="course_short_name"

=== Options ===
* Course 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 options (required)
* By pass check: Bypasses the developer-mode check (be careful!)
* Update users password: Updates the target course users password

For more help:
php admin/tool/generator/cli/maketestplan.php --help

[[es:Generador de plan de prueba JMeter]]

Test course generator

2021-07-27T09:57:10Z

Ratna: Transferred the content of https://docs.moodle.org/dev/Load_testing_Moodle_with_JMeter#Make_test_course to this page.

{{Developer tools}}
If you want a sample course for load testing or reliability of a feature (where its behaviour might depend on the size of a course), you can generate standardized test courses using the generator tool at ''Administration > Site administration > Development > Make a test course''.,

''Warning: This tool is for developer use only! Courses created using this feature can occupy a large amount of database and consume disk space (tens of gigabytes). Although you can delete those courses (and wait for various cleanup runs) to release the space they consumed, this tool should not be used on a live site. For safety it is disabled unless you set Site administration > Development > Debugging: Debug messages to DEVELOPER. ''

== Using the tool ==

# First set the debugging level to DEVELOPER as mentioned in the warning above.
# If you want to set a password for all the generated users, add the line "$CFG->tool_generator_users_password = 'YOURSECRET';" to config.php of Moodle. If the password does not comply with the site security policy to set "$CFG->passwordpolicy = 0;" too.

=== GUI version ===
# Visit Administration > Site administration > Development > Make a test course.

==== Options ====
* Size of course: You can choose amoung XS, S, M, L, XL, or XXL (required). The table below shows their difference.

Please 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.

{| 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
|}

* Short name: The course short name (required)
* Course full name and description (optional)

==== 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)

== CLI version ==

You can run the tool from the command-line using:

php admin/tool/generator/cli/maketestcourse.php

This will show command-line options.

=== Options ===
In addition to the options in the GUI version the CLI command has the following options:

* Use a fixed dataset: Use a fixed data set instead of randomly generated data, useful for generating a standard data set
* Specify a file size limit: Limits the size of the generated files to the specified number of bytes, you may find this setting useful because depending on the size you select the courses can use too much disk space
* By pass check: Bypasses the developer-mode check
* Quiet: Do not show any output

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

[[es:Generador de curso de prueba]]
[[de:Testkurs-Generator]]

User:Visvanath Ratnaweera

2013-03-31T20:53:06Z

Ratna: Deleted

Deleted [[User:Visvanath Ratnaweera|Visvanath Ratnaweera]] 04:53, 1 April 2013 (WST)

Talk:Step-by-step Installation Guide for Ubuntu

2013-03-31T20:44:13Z

Ratna: chmod 777 ???

Are you sure you going to leave the permissions at these:
<pre>sudo chmod 777 /var/moodledata
sudo chmod 777 /var/www/moodle</pre>
???
[[User:Visvanath Ratnaweera|Visvanath Ratnaweera]] 04:44, 1 April 2013 (WST)

Installing Moodle on Debian based distributions

2013-03-24T19:46:45Z

Ratna: Moved to my blog at www.syndrega.ch

Moved to http://www.syndrega.ch/?p=38.


[[Category:Installation]]
[[Category:Installation]]

File:webbench-in-vb.png

2012-04-17T14:12:22Z

Ratna: uploaded a new version of "File:webbench-in-vb.png"

File:webbench-in-vb.png

2012-04-17T14:10:49Z

Ratna:

Talk:Cron with Unix or Linux

2012-03-31T22:00:55Z

Ratna: /* Linux _is_ Unix, Mac OS too */ new section

== Since wget is being used to run the cron.php script anyway, you can really run this ANYWHERE ==
:Brought this comment from 2.0 Cron comment page. It was unsigned/undated --[[User:chris collman|chris collman]] 20:09, 22 November 2011 (WST)
It is important to note that since the cron.php script is not run internally by Moodle, but by an outside interaction, you can really run a cron job on ANY server that runs the cron.php on your Moodle installation.

So, for example, if you have a Moodle install at an ISP that does not let you run cron jobs, but you have, say, a DSLline at home, you can use any of your Linux computers at home to run cron. (you do use Linux at home, right? :)

And the beauty of it is, the crontab line is *exactly* the same as listed in the main article. It just points to an outside URL.

Now, I mention this because at one point I had configured a server to run Moodle but, in the interest of security, I did not have wget available on the server. (cron was available, but not wget).

Well, the easiest thing to do was to just run a cron job somewhere else.

Alrighty, seeyalater!

== Update and clarify ==
:Brought this comment from 2.0 Cron comment page. It was unsigned/undated --[[User:chris collman|chris collman]] 20:09, 22 November 2011 (WST)

* The whole cronclionly vs. shell invocation vs. "using wget" is completely misleading.
** while you can call cron.php using a web browser or a command line web "browser" like wget, curl, lynx from outside or inside the server. The latter commands can be scripted, e.g. to be called by cron.
** the "cronclionly" checkbox restricts the call to cron.php to calling it from inside the server and only using "bin/php". This can be scripted to be called by cron, as well.
* It should be said somewhere that using e.g. the "www-data" user in e.g. /etc/cron.d/moodle is far better than using /etc/crontab which is executed by root. AFAICS this is nowhere mentioned.

== Linux _is_ Unix, Mac OS too ==

Why does it say "Unix or Linux"? Linux _is_ Unix!

One could say "Unix (and Linux)". But then Mac OS X is Unix too.

The best is to continue with the original article [Cron] and maintain the section "Unix" (it will be valid for Linux and Mac OS X).
[[User:Visvanath Ratnaweera|Visvanath Ratnaweera]] 06:00, 1 April 2012 (WST)

User:Visvanath Ratnaweera

2012-02-27T19:55:40Z

Ratna:

{{Note|
<em>note a priori:</em> Morbi ac quam risus, ultricies faucibus odio. Fusce eu ultricies velit. Cras lobortis dolor ut leo rhoncus vulputate. Donec eget felis tellus. Duis ac odio vitae eros egestas ornare vel ut leo. Curabitur bibendum, purus sit amet ultrices tincidunt, risus sapien dignissim libero, ac semper erat nunc et nisl. Quisque aliquam ornare blandit.
}}

<blockquote>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit,</blockquote>

<h2>Section One</h2>
<p>Qua soi <abbr>abbr</abbr> Aliquam leo augue, posuere eget facilisis eu, euismod sit amet quam. Sed ultrices est vitae arcu tristique malesuada mattis nibh feugiat. Aliquam libero justo, condimentum ut consectetur facilisis, imperdiet tempus velit. Sed consequat lacinia lacus a eleifend. Cras sed magna sem</p>

<h3>Subsection One.one</h3>

<h4>Subsubsection One.one.one</h4>

<h2>Section Two</h2>
<p>Morbi gravida nisi ac metus pulvinar varius. Curabitur cursus libero metus, eu tempus lorem. Ut dictum scelerisque nisl, sit amet adipiscing velit commodo vitae. Donec a turpis enim, quis adipiscing elit. Mauris consequat euismod ligula eu eleifend. Integer nec elit risus. Donec eros nisi, laoreet eget interdum ultricies, elementum at tellus.</p>

<h3>Subsection Two.one</h3>
<p>Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

<h4>Subsection Two.two</h4>
<p>Sed quia consequuntur magni dolores eos qui ratione voluptatem<ref>Asd adf ilkaa la asdf adf adfa aaa.</ref> sequi nesciunt. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

$ <b>quo <var>vadis</var></b>
<var>apoko</var> pts/4 A.D. 2012-02-11 13:14 (:0.0)
; son qommone de mal
ghande>

<p>Curabitur mattis nisi eu nunc porttitor mattis. Praesent condimentum purus non libero blandit et viverra purus malesuada. Aliquam eget nulla vitae nunc tincidunt faucibus. Vestibulum tempus dui id quam elementum lobortis. Aliquam erat volutpat. Quisque sollicitudin lacinia orci et fringilla. Curabitur risus sem, volutpat non lobortis quis, suscipit a erat. In ac magna leo.</p>

<h2>Reference list</h2>
<references />

<h2>External links</h2>
[http://www.example.com/ http://www.example.com/] - lot of goodies


[[:Category:Nonsense:]]

User:Visvanath Ratnaweera

2012-02-25T14:40:44Z

Ratna:

{{Note|
<em>note a priori:</em> Morbi ac quam risus, ultricies faucibus odio. Fusce eu ultricies velit. Cras lobortis dolor ut leo rhoncus vulputate. Donec eget felis tellus. Duis ac odio vitae eros egestas ornare vel ut leo. Curabitur bibendum, purus sit amet ultrices tincidunt, risus sapien dignissim libero, ac semper erat nunc et nisl. Quisque aliquam ornare blandit.
}}

<blockquote>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit,</blockquote>

<h2>Section One</h2>
<p>Qua soi <abbr>abbr</abbr> Aliquam leo augue, posuere eget facilisis eu, euismod sit amet quam. Sed ultrices est vitae arcu tristique malesuada mattis nibh feugiat. Aliquam libero justo, condimentum ut consectetur facilisis, imperdiet tempus velit. Sed consequat lacinia lacus a eleifend. Cras sed magna sem</p>

<h3>Subsection One.one</h3>

<h4>Subsubsection One.one.one</h4>

<h2>Section Two</h2>
<p>Morbi gravida nisi ac metus pulvinar varius. Curabitur cursus libero metus, eu tempus lorem. Ut dictum scelerisque nisl, sit amet adipiscing velit commodo vitae. Donec a turpis enim, quis adipiscing elit. Mauris consequat euismod ligula eu eleifend. Integer nec elit risus. Donec eros nisi, laoreet eget interdum ultricies, elementum at tellus.</p>

<h3>Subsection Two.one</h3>
<p>Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

<h4>Subsection Two.two</h4>
<p>Sed quia consequuntur magni dolores eos qui ratione voluptatem<ref>Asd adf ilkaa la asdf adf adfa aaa.</ref> sequi nesciunt. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

$ <b>quo <var>vadis</var></b>
<var>apoko</var> pts/4 A.D. 2012-02-11 13:14 (:0.0)
; son qommone de mal
ghande>

<p>Curabitur mattis nisi eu nunc porttitor mattis. Praesent condimentum purus non libero blandit et viverra purus malesuada. Aliquam eget nulla vitae nunc tincidunt faucibus. Vestibulum tempus dui id quam elementum lobortis. Aliquam erat volutpat. Quisque sollicitudin lacinia orci et fringilla. Curabitur risus sem, volutpat non lobortis quis, suscipit a erat. In ac magna leo.</p>

<h2>Reference list</h2>
{{Reflist}}

<h2>External links</h2>
[http://www.example.com/ http://www.example.com/] - lot of goodies


[[:Category:Nonsense:]]

User:Visvanath Ratnaweera

2012-02-21T15:20:31Z

Ratna:

{{Note|
<em>note a priori:</em> Morbi ac quam risus, ultricies faucibus odio. Fusce eu ultricies velit. Cras lobortis dolor ut leo rhoncus vulputate. Donec eget felis tellus. Duis ac odio vitae eros egestas ornare vel ut leo. Curabitur bibendum, purus sit amet ultrices tincidunt, risus sapien dignissim libero, ac semper erat nunc et nisl. Quisque aliquam ornare blandit.
}}

<blockquote>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit,</blockquote>

<h2>Section One</h2>
<p>Qua soi <abbr>abbr</abbr> Aliquam leo augue, posuere eget facilisis eu, euismod sit amet quam. Sed ultrices est vitae arcu tristique malesuada mattis nibh feugiat. Aliquam libero justo, condimentum ut consectetur facilisis, imperdiet tempus velit. Sed consequat lacinia lacus a eleifend. Cras sed magna sem</p>

<h3>Subsection One.one</h3>

<h4>Subsubsection One.one.one</h4>

<h2>Section Two</h2>
<p>Morbi gravida nisi ac metus pulvinar varius. Curabitur cursus libero metus, eu tempus lorem. Ut dictum scelerisque nisl, sit amet adipiscing velit commodo vitae. Donec a turpis enim, quis adipiscing elit. Mauris consequat euismod ligula eu eleifend. Integer nec elit risus. Donec eros nisi, laoreet eget interdum ultricies, elementum at tellus.</p>

<h3>Subsection Two.one</h3>
<p>Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

<h4>Subsection Two.two</h4>
<p>Sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

$ <b>who <var>is there</var></b>
dodo pts/4 2012-02-11 13:14 (:0.0)
# comment or super user
mysql>

<p>Curabitur mattis nisi eu nunc porttitor mattis. Praesent condimentum purus non libero blandit et viverra purus malesuada. Aliquam eget nulla vitae nunc tincidunt faucibus. Vestibulum tempus dui id quam elementum lobortis. Aliquam erat volutpat. Quisque sollicitudin lacinia orci et fringilla. Curabitur risus sem, volutpat non lobortis quis, suscipit a erat. In ac magna leo. ></p>

User:Visvanath Ratnaweera

2012-02-21T15:17:15Z

Ratna: V1 for doc forum

{{Note|
<em>note a priori:</em> Morbi ac quam risus, ultricies faucibus odio. Fusce eu ultricies velit. Cras lobortis dolor ut leo rhoncus vulputate. Donec eget felis tellus. Duis ac odio vitae eros egestas ornare vel ut leo. Curabitur bibendum, purus sit amet ultrices tincidunt, risus sapien dignissim libero, ac semper erat nunc et nisl. Quisque aliquam ornare blandit.ppear on a yellow background.
}}

<blockquote>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit,</blockquote>

<h2>Section One</h2>
<p>Qua soi <abbr>abbr</abbr> Aliquam leo augue, posuere eget facilisis eu, euismod sit amet quam. Sed ultrices est vitae arcu tristique malesuada mattis nibh feugiat. Aliquam libero justo, condimentum ut consectetur facilisis, imperdiet tempus velit. Sed consequat lacinia lacus a eleifend. Cras sed magna sem</p>

<h3>Subsection One.one</h3>

<h4>Subsubsection One.one.one</h4>

<h2>Section Two</h2>
<p>Morbi gravida nisi ac metus pulvinar varius. Curabitur cursus libero metus, eu tempus lorem. Ut dictum scelerisque nisl, sit amet adipiscing velit commodo vitae. Donec a turpis enim, quis adipiscing elit. Mauris consequat euismod ligula eu eleifend. Integer nec elit risus. Donec eros nisi, laoreet eget interdum ultricies, elementum at tellus.</p>

<h3>Subsection Two.one</h3>
<p>Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

<h4>Subsection Two.two</h4>
<p>Sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

$ <b>who <var>is there</var></b>
dodo pts/4 2012-02-11 13:14 (:0.0)
# comment or super user
mysql>

<p>Curabitur mattis nisi eu nunc porttitor mattis. Praesent condimentum purus non libero blandit et viverra purus malesuada. Aliquam eget nulla vitae nunc tincidunt faucibus. Vestibulum tempus dui id quam elementum lobortis. Aliquam erat volutpat. Quisque sollicitudin lacinia orci et fringilla. Curabitur risus sem, volutpat non lobortis quis, suscipit a erat. In ac magna leo. ></p>

Talk:Installing Moodle on Debian based distributions

2012-02-16T17:46:25Z

Ratna: /* PHP modules and phpinfo() */ new section

TODO
Suggest that the mysql secure utility is used. I refer to it in my Amazon EC2 install page. Copy & paste from there.
Mention the various extra that need to be installed php-pear etc.
Test php by using a phpinfo page

== "Secure MySQL server" ==

Debian (and Ubuntu) MySQL server installation prompts the user to set a password for MySQL root. You can see the corr. dialog in the section MySQL, commented as (set the mysql-root password). So "mysqladmin -u root password 'new-password'" thing is obsolete.
[[User:Visvanath Ratnaweera|Visvanath Ratnaweera]] 01:40, 17 February 2012 (WST)

== PHP modules and phpinfo() ==

Yes, the list of the necessary PHP modules is incomplete.

I want to count them seperately for each Moodle version. The list for 1.9 is there, the others will come as I do a test installation for each version.

Yes, I should add the story of "phpinfo();" single liner. Will do.

Thanks for the feedback.
[[User:Visvanath Ratnaweera|Visvanath Ratnaweera]] 01:46, 17 February 2012 (WST)

Talk:Installing Moodle on Debian based distributions

2012-02-16T17:40:02Z

Ratna: /* "Secure MySQL server" */ new section

User:Visvanath Ratnaweera

2012-02-11T12:21:41Z

Ratna:

<p><blockquote>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit,</blockquote></p>

<p><blockquote>sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</blockquote></p>

<p><blockquote><cite>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam,</cite></blockquote></p>

<p><blockquote><ul>
<li><dfn>dsdf</dfn>dsdfsd</li>
<li>dsdf</li>
</ul></blockquote></p>

<p><blockquote><dl>
<dt>dsdf</dt>
<dd>sdfsdfsdfsd</dd>
<dt>dsdf</dt>
<dd>sdfsdfsdfsd</dd>
</dl></blockquote></p>

<h2>First Section</h2>
<p>Ha ha <abbr>abbr</abbr> for a <big>biiig</big> hug.</p>

<h3>Subsection</h3>

<h4>Subsubsection</h4>

<h2>Second Section</h2>

<h3>Subsection</h3>
<p>sdfds sdfsd sdfsd fdsf sdf</p>

<h4>Subsubsection</h4>
<p>Sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

<p><code>$ <b>who <var>is there</var></b><br />
rtn pts/4 2012-02-11 13:14 (:0.0)<br />
# comment or super user<br />
mysql></code></p>

<p>Sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

<p><pre>$ <b>who <var>is there</var></b>
rtn pts/4 2012-02-11 13:14 (:0.0)
# comment or super user
mysql></pre></p>

<p>Sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

User:Visvanath Ratnaweera

2012-02-11T12:17:18Z

Ratna: code or pre?

<p><blockquote>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit,</blockquote></p>

<p><blockquote>sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</blockquote></p>

<p><blockquote><cite>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam,</cite></blockquote></p>

<p><blockquote><ul>
<li><dfn>dsdf</dfn>dsdfsd</li>
<li>dsdf</li>
</ul></blockquote></p>

<p><blockquote><dl>
<dt>dsdf</dt>
<dd>sdfsdfsdfsd</dd>
<dt>dsdf</dt>
<dd>sdfsdfsdfsd</dd>
</dl></blockquote></p>

<h2>First Section</h2>
<p>Ha ha <abbr>abbr</abbr> for a <big>biiig</big> hug.</p>

<h3>Subsection</h3>

<h4>Subsubsection</h4>

<h2>Second Section</h2>

<h3>Subsection</h3>
<p>sdfds sdfsd sdfsd fdsf sdf</p>

<h4>Subsubsection</h4>
<p>Sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

<p><code>$ <b>who <var>is there</var></b><br />
rtn pts/4 2012-02-11 13:14 (:0.0)<br />
mysql></code></p>

<p>Sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

<p><pre>$ <b>who <var>is there</var></b><br />
rtn pts/4 2012-02-11 13:14 (:0.0)<br />
mysql></pre></p>

<p>Sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</p>

User:Visvanath Ratnaweera

2012-02-07T16:47:23Z

Ratna:

User:Visvanath Ratnaweera

2012-02-07T16:37:24Z

Ratna:

User:Visvanath Ratnaweera

2012-02-05T15:16:57Z

Ratna:

User:Visvanath Ratnaweera

2012-02-05T15:13:17Z

Ratna:

<h1>Top Header</h1>

<p><blockquote>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit,</blockquote></p>

<p><blockquote>sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?</blockquote></p>

<p><blockquote><cite>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam,</cite></blockquote></p>

<p><blockquote><ul>
<li><dfn>dsdf</dfn>dsdfsd</li>
<li>dsdf</li>
</ul></blockquote></p>

<p><blockquote><dl>
<dt>dsdf</dt>
<dd>sdfsdfsdfsd</dd>
<dt>dsdf</dt>
<dd>sdfsdfsdfsd</dd>
</dl></blockquote></p>

<h2>Operating System</h2>
<p>Ha ha <abbr>abbr</abbr> for a <big>biiig</big> hug.</p>

<h2>Subsection</h2>

<h3>Small subsection</h3>

<h4>Smaller subsection</h4>

<h2>Web server</h2>

<h2>Subsection</h2>

<h3>Small subsection</h3>
<code>$ <b>who <var>is there</var></b>
mysql></code>

<h4>Smaller subsection</h4>

User:Visvanath Ratnaweera

2012-02-05T11:22:28Z

Ratna: Starting to test MediaWiki HTML compatibility

<blockquote>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit,</blockquote>
<blockquote>sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?<br /><br />
<ul>
<li>dsdf</li></ul>
<cite>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam,</cite></blockquote>

<h1>Operating System</h1>
<p>Ha ha <abbr>abbr</abbr> for a <big>biiig</big> hug.</p>

<h2>Subsection</h2>

<h3>Small subsection</h3>

<h4>Smaller subsection</h4>

<h1>Web server</h1>

<h2>Subsection</h2>

<h3>Small subsection</h3>
<code>$ <b>who <var>is there</var></b>
mysql></code>

<h4>Smaller subsection</h4>

Performance FAQ

2011-06-09T11:59:22Z

Ratna: /* How do I benchmark a Moodle-site? */

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] forum, the load on the server at a particular time depends on the number of concurrent users, not on the total number of users neither on the number of users logged-in. The term "concurrent users" is used to mean those users for whom the server is actively doing something . It may by processing a webpage written in PHP, querying the database or simply transferring a file. (see also Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency])

===How do I benchmark a Moodle-site?===
You can of course benchmark parts of the system separately: the hardware as seen by the operating system (eg. CPU, disk access), web server performance, database server performance, execution on PHP operations, etc. For further details see [[Performance#Obtain_a_baseline_benchmark]].

But there is no easy formula to deduce the maximum number of concurrent users from those results. There is a PHP-script, the [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script], circulating amoung the Moodle-community which calculates a ballpark figure. The current version is attached to [http://moodle.org/mod/forum/discuss.php?d=57028&parent=772267|the posting on 25. March 2011].

Warning: Note that running this script on a production server may have unwanted side-effects. You are strongly adviced to run it on a test-site.

===What are PHP-accelerators?===
See Wikipedia [http://en.wikipedia.org/wiki/PHP_accelerator PHP accelerator].

Available software are documented under [[Performance#PHP_performance]].

You find some user suggestions here [http://moodle.org/mod/forum/discuss.php?d=168965 Update on PHP-accelerators].

===How do I cluster Moodle?===

See [[Performance#Scalability]]

[[Moodle_Clusters]]

===How do I replicate Moodle?===

[[Mirroring_Moodle]]

[http://moodle.org/mod/forum/discuss.php?d=173408&parent=760514 How to Replicate MOODLE ??!!]

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database
* networking issues (DNS, firewalls, ...)

Or your performance could be "normal" under the given circumstances:
* Are you on a dedicated server or a shared (virtual) server?
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users can you support
* what modules/activities you use? Check [[Performance#Performance of different Moodle modules]]

[[Performance#Obtain a baseline benchmark]] and compare it with the published figures.

===What are the requirements for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

This is another way of asking the same question as above. Please move up.

===Which operating system is the best?===

[[Beginning_Administration_1_FAQ#Installation_on_a_Windows_or_a_Linux_server]]

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

== See also ==
Moodle Docs
* [[Performance]]
* [[:Category:Performance]]

Forum discussions
* [http://moodle.org/mod/forum/search.php?notwords=Re:&id=5&subject=performance All performance related discussions]
* [http://moodle.org/mod/forum/search.php?notwords=Re:&id=5&forumid=33&&subject=performance Performance related discussions in the General Developer forum]

* [http://moodle.org/mod/forum/discuss.php?d=102978 1000 concurrent users]
* [http://moodle.org/mod/forum/discuss.php?d=103040 Tool to estimate server's maximum concurrent users]
* [http://moodle.org/mod/forum/discuss.php?d=144718 Handling Moodle database load - a solution!]

[[Category:FAQ]]
[[Category: Administrator]]
[[Category:Performance]]

Performance recommendations

2011-04-25T10:04:13Z

Ratna: /* Web server performance */

Location: ''Administration > Server > Performance''

Moodle can be made to perform very well, at small usage levels or scaling up to many thousands of users. The factors involved in performance are basically the same as for any PHP-based database-driven system. When trying to optimize your server, try to focus on the factor which will make the most difference to the user. For example, if you have relatively more users browsing than accessing the database, look to improve the webserver performance.

==Obtain a baseline benchmark==

Before attempting any optimization, you should obtain a baseline benchmark of the component of the system you are trying to improve. For Linux try [http://lbs.sourceforge.net/ LBS] and for Windows use the Performance Monitor. Once you have quantitative data about how your system is performing currently, you'll be able to determine if the change you have made has had any real impact.

The overall aim of adjustments to improve performance is to use RAM (cacheing) and to reduce disk-based activity. It is especially important to try to eliminate swap file usage as much as you can. If your system starts swapping, this is a sign that you need more RAM.

The '''optimization order preference''' is usually: primary storage (more RAM), secondary storage (faster hard disks/improved hard disk configuration), processor (more and faster).

==Scalability==

Moodle's design (with clear separation of application layers) allows for strongly scalable setups. (Please check the list of [[Large installations|large Moodle installations]].)

Large sites usually separate the web server and database onto separate servers, although for smaller installations this is typically not necessary.

It is possible to load-balance a Moodle installation, for example by using more than one webserver. The separate webservers should query the same database and refer to the same filestore area, but otherwise the separation of the application layers is complete enough to make this kind of clustering feasible. Similarly, the database could be a cluster of servers (e.g. a MySQL cluster), but this is not an easy task and you should seek expert support, e.g. from a Moodle Partner.

'''See also''':
*[[Server cluster]]
*[http://moodle.org/mod/forum/discuss.php?d=4801 Scalability] forum discussion.
*[http://moodle.org/mod/forum/discuss.php?d=57202 Moodle clustering] forum discussion.
*[http://moodle.org/mod/forum/discuss.php?d=44470 Software load balancing] forum discussion.
*[http://moodle.org/mod/forum/discuss.php?d=49986 TCP load balancing] forum dicsussion.

==Hardware configuration==
'''Note''': The fastest and most effective change that you can make to improve performance is to '''increase the amount of RAM on your web server''' - get as much as possible (eg 4GB). Increasing primary memory will reduce the need for processes to swap to disk and will enable your server to handle more users.
* Better performance is gained by obtaining the best '''processor capability''' you can, i.e. dual or dual core processors. A modern BIOS should allow you to enable hyperthreading, but check if this makes a difference to the overall performance of the processors by using a [http://en.wikipedia.org/wiki/Super_PI CPU benchmarking tool].
* If you can afford them, use '''SCSI hard disks''' instead of SATA drives. SATA drives will increase your system's CPU utilization, whereas SCSI drives have their own integrated processors and come into their own when you have multiple drives. If you must have SATA drives, check that your motherboard and the drives themselves support NCQ (Native Command Queuing).
* Purchase hard disks with a '''low seek time'''. This will improve the overall speed of your system, especially when accessing Moodle's reports.
* Size your '''swap file''' correctly. The general advice is to set it to 4 x physical RAM.
* Use a '''RAID disk system'''. Although there are many different RAID configurations you can create, the following generally works best:
** install a hardware RAID controller (if you can)
** the operating system and swap drive on one set of disks configured as RAID-1.
** Moodle, Web server and Database server on another set of disks configured as RAID-5.
* Use '''gigabit ethernet''' for improved latency and throughput. This is especially important when you have your webserver and database server separated out on different hosts.
* Check the settings on your '''network card'''. You may get an improvement in performance by increasing the use of buffers and transmit/receive descriptors (balance this with processor and memory overheads) and off-loading TCP checksum calculation onto the card instead of the OS.
* Read this [http://moodle.org/mod/forum/discuss.php?d=68579 Case Study] on a server stress test with 300 users.
* See this [http://elearning.sgu.ac.jp/doc/PT/ accompanying report] on network traffic and server loads.
* See the [[Moodle.org configuration]]
* Also see this SFSU presentation at Educause (using VMWare): [http://www.educause.edu/Resources/AnOpenSourceLMSforaMissionCrit/162843]

==Operating System==
* You can use [http://en.wikipedia.org/wiki/Linux Linux](recommended), Unix-based, Windows or Mac OS X for the server '''operating system'''. *nix operating systems generally require less memory than Mac OS X or Windows servers for doing the same task as the server is configured with just a shell interface. Additionally Linux does not have licensing fees attached, but can have a big learning curve if you're used to another operating system. If you have a large number of processors running SMP, you may also want to consider using a highly tuned OS such as [http://en.wikipedia.org/wiki/Solaris_Operating_Environment Solaris].
* Check your own OS and '''vendor specific instructions''' for optimization steps.
** For Linux look at the [http://linuxperf.sourceforge.net/ Linux Performance Team] site.
** For Linux investigate the hdparm command, e.g. hdparm -m16 -d1 can be used to enable read/write on multiple sectors and DMA. Mount disks with the async and noatime options.
** For Windows set the sever to be optimized for network applications (Control Panel, Network Connections, LAN connection, Properties, File & Printer Sharing for Microsoft Networks, Properties, Optimization). You can also search the [http://technet.microsoft.com/ Microsoft TechNet site] for optimization documents.

==Web server performance==

Installing [http://www.mozilla.com/en-US/ Firefox] and the [https://addons.mozilla.org/en-US/firefox/addon/1843 firebug] extension will allow you to watch the time it takes for each page component to load. Also, the [https://addons.mozilla.org/en-US/firefox/addon/5369 Yslow] extension will evaluate your page against Yahoo's [http://www.skrenta.com/2007/05/14_rules_for_fast_web_pages_by_1.html 14 rules], full text [http://developer.yahoo.com/performance/rules.html Best Practices for Speeding Up Your Web Site], <strike>([http://video.yahoo.com/video/play?vid=1040890 video])</strike> for fast loading websites.

===PHP performance===
* You are strongly recommended to use a '''PHP accelerator''' to ease CPU load, such as [http://pecl.php.net/apc APC], [http://www.php-accelerator.co.uk/ PHPA], [http://trac.lighttpd.net/xcache/ Xcache] or [http://eaccelerator.net/ eAccelerator]. (Take care to choose a PHP accelerator that is known to work well with your version of PHP and note that Turck MMCache is [http://turckmmcache.exeprod.com/TheManifestoEnglish no longer maintained] and can cause failures with PHP 5).
* Improvements in read/write performance can be improved by putting the cached PHP pages on a [[TMPFS]] filesystem - but remember that you'll lose the cache contents when there is a power failure or the server is rebooted.
* Performance of PHP is better when installed as an '''Apache/IIS ISAPI module''' (rather than a CGI).
* Also check the '''memory_limit''' in php.ini, reduce it to 16M for Moodle version earlier than 1.7 ([http://moodle.org/mod/forum/discuss.php?d=39656 See this forum discussion]). For Moodle 1.7 or later, it is recommended that the value of memory_limit should be 40M. As of [http://www.php.net/ChangeLog-5.php PHP 5.2.1] the default value for the memory_limit directive is 128M.
* Also see [[PHP_settings_by_Moodle_version]]

===Install HowTo===
* [http://2bits.com/articles/installing-php-apc-gnulinux-centos-5.html APC on CentOS 5.x (linux)]
* [http://fplanque.com/dev/linux/install-apc-php-cache-debian-lenny APC on Debian (linux)]
* [http://www.linuxtuts.net/211-installing-memcached-php5-memcache-module-debian-apache2.html MemCache module on Debian (Apache2 and PHP5) ]
* [http://noveckg.blogspot.com/2010/03/installing-memcached-on-centos-5x.html Installing Memcache on CentOS 5.x (linux)]
* [http://noveckg.blogspot.com/2010/02/installing-eaccelerator-cache-for-php.html Installing eAccelerator on CentOS 5.x (linux)]
* [https://docs.moodle.org/en/Installing_eAccelerator_In_Ubuntu_Server/ Installing eAccelerator on Ubuntu Server (linux)]

===Apache performance===
* If you are using Apache on a Windows server, use the build from [http://www.apachelounge.com Apache Lounge] which is reported to have [http://moodle.org/mod/forum/discuss.php?d=93358 performance and stability improvements] compared to the official Apache download. Note that this is an unofficial build, so may not keep up with official releases.
* Set the '''MaxClients''' directive correctly. Use this formula to help (which uses 80% of available memory to leave room for spare):
MaxClients = Total available memory * 80% / Max memory usage of apache process
:Memory usage of apache process is usually 10MB, so a general rule of thumb is to divide your available memory in megabytes by 10 to get the value of MaxClients. To find the max memory usage of apache processes read the value from the shell command:
#ps -ylC httpd --sort:rss

:If you need to increase the value of '''MaxClients''' beyond 256, you will also need to set the '''ServerLimit''' directive.

:'''Warning''': Do not be tempted to set the value of MaxClients higher than your available memory as your server will consume more RAM than available and start to swap to disk.
* Consider reducing the '''number of modules''' that Apache loads in the httpd.conf file to the minumum necessary to reduce the memory needed.
* Use the '''latest version of Apache''' - Apache 2 has an improved memory model which reduces memory usage further.
* For Unix/Linux systems, consider lowering '''MaxRequestsPerChild''' in httpd.conf to as low as 20-30 (if you set it any lower the overhead of forking begins to outweigh the benefits).
* For a heavily loaded server, consider setting '''KeepAlive Off''' (do this only if your Moodle pages do not contain links to resources or uploaded images) or lowering the '''KeepAliveTimeout''' to between 2 and 5. The default is 15 (seconds) - the higher the value the more server processes will be kept waiting for possibly idle connections. A more accurate value for KeepAliveTimeout is obtained by observing how long it takes your users to download a page. After altering any of the KeepAlive variables, monitor your CPU utilization as there may be an additional overhead in initiating more worker processes/threads.
* A warning about the previous performance tip. Microsoft Internet Explorer has a (little) known bug that causes seriously problems with SSL-enabled Apache websites. The issue is that if a web server's KeepAlive timeout is set to less than 60 seconds (say to the default of 15 seconds), MSIE can get confused about whether a keep-alive connection is available or not. As a result, any browser POST requests (which always use a keep-alive if available) will fail to reach the server. This is easily reproduced with postings to the Moodle forums. Using MSIE, connect to an ssl-enabled Moodle site. Write a quick forum post, and submit it when the form has been displayed for between 15 seconds and 60 seconds. You will see a browser error message, and your post content will be lost. In some cases, doing this will even crash the Windows TCP stack on the client machine. ''' So, if your site is SSL-enabled, and you use Apache, you should set the KeepAliveTimeout to at least 60 seconds'''.
* As an alternative to using KeepAlive Off, consider setting-up a '''Reverse Proxy server''' infront of the Moodle server to cache HTML files with images. You can then return Apache to using keep-alives on the Moodle server.
* If you do not use a .htaccess file, set the '''AllowOverride''' variable to AllowOverride None to prevent .htaccess lookups.
* Set '''DirectoryIndex''' correctly so as to avoid content-negotiation. Here's an example from a production server:
DirectoryIndex index.php index.html index.htm
* Unless you are doing development work on the server, set '''ExtendedStatus Off''' and disable mod_info as well as mod_status.
* Leave '''HostnameLookups Off''' (as default) to reduce DNS latency.
* Consider reducing the value of '''TimeOut''' to between 30 to 60 (seconds).
* For the '''Options directive''', avoid Options Multiviews as this performs a directory scan. To reduce disk I/O further use
Options -Indexes FollowSymLinks
*'''Caching (unsupported)''' - ''Please note that this kind of caching may create major problems during upgrades.'' Apache can be told to make pages load a lot faster by specifying that the browser should cache some various page elements such as images and reuse them from local memory rather than ask for them again every time a page is requested. How to do this varies slightly between OSes but there are two basic steps:

# Install and enable mod_expires - refer to documentation or man pages
# Add this code to the virtual server config file within the <directory> section for the root directory (or within the .htaccess file if AllowOverrides is On):
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 1 seconds"
ExpiresByType text/html "access plus 1 seconds"
ExpiresByType image/gif "access plus 1 week"
ExpiresByType image/jpeg "access plus 1 week"
ExpiresByType image/png "access plus 1 week"
ExpiresByType text/css "access plus 1 week"
ExpiresByType text/javascript "access plus 1 week"
ExpiresByType application/x-javascript "access plus 1 week"
ExpiresByType text/xml "access plus 1 seconds"
</IfModule>

The effect is to make everything stay in the cache except HTML and XML, which change dynamically. It's possible to gain a several hundred percent decrease in load times this way. Adjust the cache times according to how often your images etc change.

* Compression reduces response times by reducing the size of the HTTP response
# Install and enable mod_deflate - refer to documentation or man pages
# Add this code to the virtual server config file within the <directory> section for the root directory (or within the .htaccess file if AllowOverrides is On):
<ifModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/html text/plain text/xml
</ifmodule>

More info: [http://www.metaskills.net/blog/heuristics/sysadmin/how-to-control-browser-caching-with-apache-2 www.metaskills.net]

===IIS performance===
All alter this location in the registry:
HKLM\SYSTEM\CurrentControlSet\Services\Inetinfo\Parameters\
* The equivalent to KeepAliveTimeout is '''ListenBackLog''' (IIS - registry location is HKLM\ SYSTEM\ CurrentControlSet\ Services\ Inetinfo\ Parameters). Set this to between 2 to 5.
*Change the '''MemCacheSize''' value to adjust the amount of memory (Mb) that IIS will use for its file cache (50% of available memory by default).
*Change the '''MaxCachedFileSize''' to adjust the maximum size of a file cached in the file cache in bytes. Default is 262,144 (256K).
*Create a new DWORD called '''ObjectCacheTTL''' to change the length of time (in milliseconds) that objects in the cache are held in memory. Default is 30,000 milliseconds (30 seconds).

===Lighttpd, NginX and Cherokee performance===
You can increase server performance by using a '''light-weight''' webserver like [http://www.lighttpd.net/ lighttpd], [http://nginx.net/ nginx] or [http://www.cherokee-project.com/ cherokee] in combination with PHP in FastCGI-mode. Lighttpd was originally created as a proof-of-concept[http://www.lighttpd.net/story] to address the [http://www.kegel.com/c10k.html C10k problem] and while primarily recommended for memory-limited servers, its design origins and asynchronous-IO model make it a suitable and proven[http://blog.lighttpd.net/articles/2006/12/28/lighttpd-powers-5-alexa-top-250-sites] alternative HTTP server for high-load websites and web apps, including Moodle. See the [[lighttpd | MoodleDocs Lighttpd page]] for additional information, configuration example and links.

Alternatively, both [http://www.lighttpd.net/ lighttpd] and [http://nginx.net/ nginx] are capable of performing as a load-balancer and/or reverse-proxy to alleviate load on back-end servers[http://www.linuxjournal.com/article/10108], providing benefit without requiring an actual software change on existing servers.

Do note that these are likely to be the least tested server environments of all particularly if you are using advanced features such as web services and/or Moodle Networking. They are probably best considered for heavily used Moodle sites with relatively simple configurations.

==Database performance==

Moodle contains a script which will display some key database performance statistics from the [http://phplens.com/lens/adodb/docs-perf.htm ADOdb performance monitor]. Run the script in your browser as in the following example:

http://www.mymoodle.com/admin/dbperformance.php

Use the data displayed as a guide to tune and improve the performance of your database server.

===MySQL performance===

The following are MySQL specific settings which can be adjusted for better performance in your my.cnf (my.ini in Windows). The file contains a list of settings and their values. To see the current values use these commands
SHOW STATUS;
SHOW VARIABLES;
'''Important''': You must make backups of your database before attempting to change any MySQL server configuration. After any change to the my.cnf, restart mysqld.

If you are able, the [http://mysqltuner.com/ MySQLTuner] tool can be run against your MySQL server and will calculate appropriate configuration values for most of the following settings based on your current load, status and variables automatically.

* Enable the '''query cache''' with
query_cache_type = 1.
For most Moodle installs, set the following:
query_cache_size = 36M
query_cache_min_res_unit = 2K.
The query cache will improve performance if you are doing few updates on the database.
* Set the '''table cache''' correctly. For Moodle 1.6 set
table_cache = 256 #(table_open_cache in MySQL > 5.1.2)
(min), and for Moodle 1.7 set
table_cache = 512 #(table_open_cache in MySQL > 5.1.2)
(min). The table cache is used by all threads (connections), so monitor the value of opened_tables to further adjust - if opened_tables > 3 * table_cache(table_open_cache in MySQL > 5.1.2) then increase table_cache upto your OS limit. Note also that the figure for table_cache will also change depending on the number of modules and plugins you have installed. Find the number for your server by executing the mysql statement below. Look at the number returned and set table_cache to this value.
mysql>SELECT COUNT(table_name) FROM information_schema.tables WHERE table_schema='yourmoodledbname';
* Set the '''thread cache''' correctly. Adjust the value so that your thread cache utilization is as close to 100% as possible by this formula:
thread cache utilization (%) = (threads_created / connections) * 100
* The '''key buffer''' can improve the access speed to Moodle's SELECT queries. The correct size depends on the size of the index files (.myi) and in Moodle 1.6 or later (without any additional modules and plugins), the recommendation for this value is key_buffer_size = 32M. Ideally you want the database to be reading once from the disk for every 100 requests so monitor that the value is suitable for your install by adjusting the value of key_buffer_size so that the following formulas are true:
key_read / key_read_requests < 0.01
key_write / key_write_requests <= 1.0
* Set the '''maximum number of connections''' so that your users will not see a "Too many connections" message. Be careful that this may have an impact on the total memory used. MySQL connections usually last for milliseconds, so it is unusual even for a heavily loaded server for this value to be over 200.
* Manage '''high burst activity'''. If your Moodle install uses a lot of quizzes and you are experiencing performance problems (check by monitoring the value of threads_connected - it should not be rising) consider increasing the value of back_log.
* '''Optimize your tables weekly and after upgrading Moodle'''. It is good practice to also optimize your tables after performing a large data deletion exercise, e.g. at the end of your semester or academic year. This will ensure that index files are up to date. Backup your database first and then use:
mysql>CHECK TABLE mdl_tablename;
mysql>OPTIMIZE TABLE mdl_tablename;
:The common tables in Moodle to check are mdl_course_sections, mdl_forum_posts, mdl_log and mdl_sessions (if using dbsessions). Any errors need to be corrected using REPAIR TABLE (see the [http://dev.mysql.com/doc/refman/5.0/en/repair-table.html MySQL manual] and this [http://moodle.org/mod/forum/discuss.php?d=58208#p279638 forum script]).
* '''Maintain the key distribution'''. Every month or so it is a good idea to stop the mysql server and run these myisamchk commands.
#myisamchk -a -S /pathtomysql/data/moodledir/*.MYI
:'''Warning''': You must stop the mysql database process (mysqld) before running any myisamchk command. If you do not, you risk data loss.
* Reduce the number of '''temporary tables saved to disk'''. Check this with the created_tmp_disk_tables value. If this is relatively large (>5%) increase tmp_table_size until you see a reduction. Note that this will have an impact on RAM usage.

===PostgreSQL performance===

There are some good papers around on tuning PostgreSQL, and Moodle's case does not seem to be different to the general case.

The first thing to recognise is that if you really need to worry about tuning you should be using a separate machine for the database server. If you are not using a separate machine then the answers to many performance questions are substantially muddied by the memory requirements of the rest of the application.

You should probably '''enable autovacuum''', unless you know what you are doing. Many e-learning sites have predictable periods of low use, so disabling autovacuum and running a specific vacuum at those times can be a good option. Or perhaps leave autovacuum running but do a full vacuum weekly in a quiet period.

Set '''shared_buffers''' to something reasonable. For versions up to 8.1 my testing has shown that peak performance is almost always obtained with buffers < 10000, so if you are using such a version, and have more than 512M of RAM just set shared_buffers to 10,000 (8MB).

The buffer management had a big overhaul in 8.2 and "reasonable" is now a much larger number. I have not conducted performance tests with 8.2, but the recommendations from others are generally that you should now scale shared_buffers much more with memory and may continue to reap benefits even up to values like 100,000 (80MB). Consider using 1-2% of system RAM.

PostgreSQL will also assume that the operating system is caching its files, so setting '''effective_cache_size''' to a reasonable value is also a good idea. A reasonable value will usually be (total RAM - RAM in use by programs). If you are running Linux and leave the system running for a day or two you can look at 'free' and under the 'cached' column you will see what it currently is. Consider taking that number (which is kB) and dividing it by 10 (i.e. allow 20% for other programs cache needs and then divide by 8 to get pages). If you are not using a dedicated database server you will need to decrease that value to account for usage by other programs.

Some other useful parameters that can have positive effects, and the values I would typically set them to on a machine with 4G RAM, are:

work_mem = 10240

That's 10M of RAM to use instead of on-disk sorting and so forth. That can give a big speed increase, but it is per connection and 200 connections * 10M is 2G, so it can theoretically chew up a lot of RAM.

maintenance_work_mem = 163840

That's 160M of RAM which will be used by (e.g.) VACUUM, index rebuild, cluster and so forth. This should only be used periodically and should be freed when those processes exit, so I believe it is well worth while.

max_fsm_pages = 100000
max_fsm_relations = 5000

These are used to hold the free-space map, and if they are too small you will see performance degradation after the database has been operating for some time. The exact numbers to set can be gleaned from the output of VACUUM VERBOSE, which prints the required FSM pages at the end of it's run. The 5x increase seems to be useful for a Moodle installation, from experience.

wal_buffers = 64

These buffers are used for the write-ahead log, and there have been a number of reports on the PostgreSQL mailing lists of improvement from this level of increase.

This is a little out of date now (version 8.0) but still worth a read: http://www.powerpostgresql.com/Docs

And there is lots of good stuff here as well: http://www.varlena.com/GeneralBits/Tidbits/index.php

''Based on Andrew McMillan's post at [http://moodle.org/mod/forum/discuss.php?d=68558 Tuning PostgreSQL] forum thread.''

===Other database performance links===
* Consider using a '''distributed cacheing system''' like [http://en.wikipedia.org/wiki/Memcached memcached] but note that memcached does not have any security features so it should be used behind a firewall.
* Consider using PostgreSQL. See [[Arguments in favour of PostgreSQL]] and [http://moodle.org/mod/forum/discuss.php?d=49195 how to migrate from MySQL to PostgreSQL] (forum discussion).
* [[Increasing the database connection lifetime | Try increasing the database connection lifetime]]
* [http://dev.mysql.com/doc/refman/5.0/en/server-parameters.html General advice on tuning MySQL parameters] (advice from the MySQL manual)
* [http://www.mysqlperformanceblog.com/2007/11/01/innodb-performance-optimization-basics/ InnoDB performance optimization] taken from the [http://www.mysqlperformanceblog.com/ MySQL performance blog] site.

==Moodle Admin settings==
* In Moodle 1.7 or later, set the '''Cache type''' for your server: Site Admin -> Server -> Performance -> Cache type. There are several options available.
:*If you do not have eaccelerator or mmemcached installed, choose "internal" (which makes use of the record/internal cache - see the next bullet point).
:* If you have a single server and have compiled '''eaccelerator with shared memory support''', set the cache type to the eaccelerator option.
:* If you have a '''separate memcached server''', set the cache type to memcached and enter a csv list of server IP addresses.
* Enable the '''record/internal cache''': Site Admin -> Server -> Performance -> Record cache = True. Set the maximum amount of memory allocated to the cache in the Int Cache Max box. This will enable a primary cache for database records, without using any database engine cache, e.g. MySQL/PostgreSQL cache. See [http://tracker.moodle.org/browse/MDL-7196 this Tracker entry] for a full discussion.
* Enable the '''language cache'''.
* Large log files can cause overall performance to degrade over time. If you observe that the site has gradually got slower loading pages in the browser, '''reduce your Log life time''' setting (Admin/Server/Cleanup).
* Performance can be greatly improved by allowing Moodle to use the system '''zip/unzip''' commands (rather than PHP-based zip libraries) - visit Admin/Server/System Paths and enter the path to the relevant executables. (Similarly, filling in the path to '''du''' will improve Moodle's speed at listing directory contents.)
* Note that using '''secure web connections''' ('''https''' rather than '''http''') carries a higher processing burden, both for the webserver and the client - particularly because cacheing cannot be used as effectively, so the number of file requests is likely to increase dramatically. For this reason using https for all Moodle pages is not recommended. You can enable https just for the login screen, simply from Moodle's config page.
* Check your '''filters'''. Having too many filters active can have serious effects on server load, especially on lower-end systems. The number of active filters has a direct effect on the perceived latency of your site; that is the time taken for each page impression.
* Enable the '''text cache''' but do not "Filter all strings" unless you have a specific need. If in doubt profile the performance, and see how your changes affect the processing time.
* Check your '''anti-virus''' measures on the server. Although they are useful for preventing security holes being exploited, some "On-Demand" scanners can affect performance by scanning page content (word, ppt files etc).
* If there are performance problems loading course pages, check the '''Resource module settings'''. The setting resource_filterexternalpages is known to slow-down course pages and should be set to 'No' for better performance.
* Check your '''forum settings'''. To improve performance set forum_trackreadposts = No and forum_usermarksread = Yes (this will impact on the convenience of your users' forum experience). Also consider setting the time of the day when old posts are cleared from the read table (forum_cleanreadtime) to when your site is less busy.
* Don't use database sessions unless you really need them. On-disc sessions tend to be much faster.

==Performance of different Moodle modules==

Moodle's activity modules, filters, and other plugins can be activated/deactivated. If necessary, you may wish to deactivate some features (such as chat) if not required - but this isn't necessary. Some notes on the performance of certain modules:

* The '''Chat''' module is [http://moodle.org/mod/forum/discuss.php?d=37979&parent=175079 said] to be a hog in terms of frequent HTTP requests to the main server. This can be reduced by setting the module to use ''Streamed'' updates, or, if you're using a Unix-based webserver, by running the chat in daemon mode. When using the Chat module use the configuration settings to tune for your expected load. Pay particular attention to the ''chat_old_ping'' and ''chat_refresh'' parameters as these can have greatest impact on server load.
* The '''Quiz''' module is known to stretch database performance. Try to optimise your database server by tuning. See [http://moodle.org/mod/forum/discuss.php?d=25616&parent=120770 for a brief report on performance for 55 students simultaneously using quizzes]
** See this Case Study for an extensive server stress test with 300 quiz users.[http://moodle.org/mod/forum/discuss.php?d=68579] And this accompanying report on network traffic and server loads. [http://elearning.sgu.ac.jp/doc/PT/]
* The Moodle '''Cron''' task is triggered by calling the script ''cron.php''. If this is called over HTTP (e.g. using wget or curl) it can take a large amount of memory on large installations. If it is called by directly invoking the php command (e.g. ''php -f /path/to/moodle/directory/admin/cron.php'') efficiency can be much improved.
* The '''Recent activities''' block is consuming to much resources if you have huge number of records <code>mdl_log</code>. this is being tested to optimize the SQL query.

==Moodle Image Optimization==

The base images delivered in the original Moodle distribution package provide unoptimized graphics, most of which can benefit from lossless recompression utilizing [http://optipng.sourceforge.net/ optipng] for PNGs, [http://www.lcdf.org/gifsicle/ gifsicle] for GIFs and [http://www.kokkonen.net/tjko/projects.html jpegoptim] for JPGs. Optimized graphics transfer faster and provide a faster perceived response for clients[http://www.websiteoptimization.com/speed/12/], especially distance learners. The following example will recursively optimize (without any loss of quality) all the graphics and image files included in a base Moodle installation directory on a server with the above commands installed and available.

<pre>
find /example/directory/moodle-1.9 -iname *.png -exec optipng -o7 {} \;
find /example/directory/moodle-1.9 -iname *.gif -exec gifsicle -O2 -b {} \;
find /example/directory/moodle-1.9 -iname *.jpg -exec jpegoptim -p {} \;
</pre>

Both [http://optipng.sourceforge.net/ optipng] and [http://www.lcdf.org/gifsicle/ gifsicle] are provided in the base repositories of most newer Linux distributions; [http://www.kokkonen.net/tjko/projects.html jpegoptim] must be downloaded and installed manually.

==See also==

*[[Performance FAQ]]
*Using Moodle: [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance] forum

There have been a lot of discussions on moodle.org about performance, here are some of the more interesting and (potentially) useful ones:

* [http://moodle.org/mod/forum/discuss.php?d=83057 Performance woes!]
* [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script]
* [http://moodle.org/mod/forum/discuss.php?d=88927 Comments on planned server hardware]
* [http://moodle.org/mod/forum/discuss.php?d=102978#p461624 Moodle performance in a pil by Martin Langhoff]
[[Category:Performance]]

[[es:Rendimiento]]
[[fr:Performance]]
[[ja:パフォーマンス]]
[[pl:Wydajnosc]]

Performance FAQ

2011-04-25T09:55:39Z

Ratna: /* Which operating system is the best? */

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] forum, the load on the server at a particular time depends on the number of concurrent users, not on the total number of users neither on the number of users logged-in. The term "concurrent users" is used to mean those users for whom the server is actively doing something . It may by processing a webpage written in PHP, querying the database or simply transferring a file. (see also Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency])

===How do I benchmark a Moodle-site?===
You can of course benchmark parts of the system separately: hardware as seen by the operating system (eg. disk access speed), web server performance, database server performance, execution of PHP, etc. For further information see [[Performance#Obtain_a_baseline_benchmark]].

But there is no easy formula to deduct the maximum number of concurrent users from those results. There is a PHP-script, the [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script], circulating amoung the Moodle-community which calculates a ballpark figure. The current version is attached to [http://moodle.org/mod/forum/discuss.php?d=57028#p296907 the posting on 1. March 2007].

Warning: Note that running this script on a production server may have unwanted side-effects. You are strongly adviced to run it on a test-site.

===What are PHP-accelerators?===
See Wikipedia [http://en.wikipedia.org/wiki/PHP_accelerator PHP accelerator].

Available software are documented under [[Performance#PHP_performance]].

You find some user suggestions here [http://moodle.org/mod/forum/discuss.php?d=168965 Update on PHP-accelerators].

===How do I cluster Moodle?===

See [[Performance#Scalability]]

[[Moodle_Clusters]]

===How do I replicate Moodle?===

[[Mirroring_Moodle]]

[http://moodle.org/mod/forum/discuss.php?d=173408&parent=760514 How to Replicate MOODLE ??!!]

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database
* networking issues (DNS, firewalls, ...)

Or your performance could be "normal" under the given circumstances:
* Are you on a dedicated server or a shared (virtual) server?
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users can you support
* what modules/activities you use? Check [[Performance#Performance of different Moodle modules]]

[[Performance#Obtain a baseline benchmark]] and compare it with the published figures.

===What are the requirements for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

This is another way of asking the same question as above. Please move up.

===Which operating system is the best?===

[[Beginning_Administration_1_FAQ#Installation_on_a_Windows_or_a_Linux_server]]

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

== See also ==
Moodle Docs
* [[Performance]]
* [[:Category:Performance]]

Forum discussions
* [http://moodle.org/mod/forum/search.php?notwords=Re:&id=5&subject=performance All performance related discussions]
* [http://moodle.org/mod/forum/search.php?notwords=Re:&id=5&forumid=33&&subject=performance Performance related discussions in the General Developer forum]

* [http://moodle.org/mod/forum/discuss.php?d=102978 1000 concurrent users]
* [http://moodle.org/mod/forum/discuss.php?d=103040 Tool to estimate server's maximum concurrent users]
* [http://moodle.org/mod/forum/discuss.php?d=144718 Handling Moodle database load - a solution!]

[[Category:FAQ]]
[[Category: Administrator]]
[[Category:Performance]]

Performance FAQ

2011-04-25T09:49:17Z

Ratna: /* How do I replicate Moodle? */

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] forum, the load on the server at a particular time depends on the number of concurrent users, not on the total number of users neither on the number of users logged-in. The term "concurrent users" is used to mean those users for whom the server is actively doing something . It may by processing a webpage written in PHP, querying the database or simply transferring a file. (see also Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency])

===How do I benchmark a Moodle-site?===
You can of course benchmark parts of the system separately: hardware as seen by the operating system (eg. disk access speed), web server performance, database server performance, execution of PHP, etc. For further information see [[Performance#Obtain_a_baseline_benchmark]].

But there is no easy formula to deduct the maximum number of concurrent users from those results. There is a PHP-script, the [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script], circulating amoung the Moodle-community which calculates a ballpark figure. The current version is attached to [http://moodle.org/mod/forum/discuss.php?d=57028#p296907 the posting on 1. March 2007].

Warning: Note that running this script on a production server may have unwanted side-effects. You are strongly adviced to run it on a test-site.

===What are PHP-accelerators?===
See Wikipedia [http://en.wikipedia.org/wiki/PHP_accelerator PHP accelerator].

Available software are documented under [[Performance#PHP_performance]].

You find some user suggestions here [http://moodle.org/mod/forum/discuss.php?d=168965 Update on PHP-accelerators].

===How do I cluster Moodle?===

See [[Performance#Scalability]]

[[Moodle_Clusters]]

===How do I replicate Moodle?===

[[Mirroring_Moodle]]

[http://moodle.org/mod/forum/discuss.php?d=173408&parent=760514 How to Replicate MOODLE ??!!]

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database
* networking issues (DNS, firewalls, ...)

Or your performance could be "normal" under the given circumstances:
* Are you on a dedicated server or a shared (virtual) server?
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users can you support
* what modules/activities you use? Check [[Performance#Performance of different Moodle modules]]

[[Performance#Obtain a baseline benchmark]] and compare it with the published figures.

===What are the requirements for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

This is another way of asking the same question as above. Please move up.

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

== See also ==
Moodle Docs
* [[Performance]]
* [[:Category:Performance]]

Forum discussions
* [http://moodle.org/mod/forum/search.php?notwords=Re:&id=5&subject=performance All performance related discussions]
* [http://moodle.org/mod/forum/search.php?notwords=Re:&id=5&forumid=33&&subject=performance Performance related discussions in the General Developer forum]

* [http://moodle.org/mod/forum/discuss.php?d=102978 1000 concurrent users]
* [http://moodle.org/mod/forum/discuss.php?d=103040 Tool to estimate server's maximum concurrent users]
* [http://moodle.org/mod/forum/discuss.php?d=144718 Handling Moodle database load - a solution!]

[[Category:FAQ]]
[[Category: Administrator]]
[[Category:Performance]]

Performance FAQ

2011-04-25T09:42:36Z

Ratna:

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] forum, the load on the server at a particular time depends on the number of concurrent users, not on the total number of users neither on the number of users logged-in. The term "concurrent users" is used to mean those users for whom the server is actively doing something . It may by processing a webpage written in PHP, querying the database or simply transferring a file. (see also Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency])

===How do I benchmark a Moodle-site?===
You can of course benchmark parts of the system separately: hardware as seen by the operating system (eg. disk access speed), web server performance, database server performance, execution of PHP, etc. For further information see [[Performance#Obtain_a_baseline_benchmark]].

But there is no easy formula to deduct the maximum number of concurrent users from those results. There is a PHP-script, the [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script], circulating amoung the Moodle-community which calculates a ballpark figure. The current version is attached to [http://moodle.org/mod/forum/discuss.php?d=57028#p296907 the posting on 1. March 2007].

Warning: Note that running this script on a production server may have unwanted side-effects. You are strongly adviced to run it on a test-site.

===What are PHP-accelerators?===
See Wikipedia [http://en.wikipedia.org/wiki/PHP_accelerator PHP accelerator].

Available software are documented under [[Performance#PHP_performance]].

You find some user suggestions here [http://moodle.org/mod/forum/discuss.php?d=168965 Update on PHP-accelerators].

===How do I cluster Moodle?===

See [[Performance#Scalability]]

[[Moodle_Clusters]]

===How do I replicate Moodle?===

[[Mirroring_Moodle]]

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database
* networking issues (DNS, firewalls, ...)

Or your performance could be "normal" under the given circumstances:
* Are you on a dedicated server or a shared (virtual) server?
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users can you support
* what modules/activities you use? Check [[Performance#Performance of different Moodle modules]]

[[Performance#Obtain a baseline benchmark]] and compare it with the published figures.

===What are the requirements for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

This is another way of asking the same question as above. Please move up.

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

== See also ==
Moodle Docs
* [[Performance]]
* [[:Category:Performance]]

Forum discussions
* [http://moodle.org/mod/forum/search.php?notwords=Re:&id=5&subject=performance All performance related discussions]
* [http://moodle.org/mod/forum/search.php?notwords=Re:&id=5&forumid=33&&subject=performance Performance related discussions in the General Developer forum]

* [http://moodle.org/mod/forum/discuss.php?d=102978 1000 concurrent users]
* [http://moodle.org/mod/forum/discuss.php?d=103040 Tool to estimate server's maximum concurrent users]
* [http://moodle.org/mod/forum/discuss.php?d=144718 Handling Moodle database load - a solution!]

[[Category:FAQ]]
[[Category: Administrator]]
[[Category:Performance]]

Performance FAQ

2009-10-31T16:25:00Z

Ratna: /* How many users will my installation support? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] fourm, the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something (see Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency]). It may by processing a webpage written in PHP, querrying the database or simply transfering a file.

===How do I benchmark a Moodle-site?===
You can of course benchmark each component of the software stack: operating system, webserver, database server, PHP (see [[Performance#Obtain_a_baseline_benchmark]]). But there is no easy formula to deduct the maximum number of concurrent users from those results.

There is a PHP-script, the [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script], circulating amoung the Moodle-community which calculates a ballpark figure. The current version is attached to the [http://moodle.org/mod/forum/discuss.php?d=57028#p296907 posting on 1. March 2007].

Warning: Note that running this script on a production server may have unwanted side-effects. You are strongly adviced to run it on a test-site.

===What are PHP-accelerators?===
See Wikipedia article [http://en.wikipedia.org/wiki/PHP_accelerator PHP accelerator].

Available software are documented [[Performance#PHP_performance]].

===How do I cluster Moodle?===

See [[Performance#Scalability]]

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [[Performance#Performance of different Moodle modules]]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[[Performance#Obtain a baseline benchmark]] and compare it with the published figures.

See also:
* [http://moodle.org/mod/forum/discuss.php?d=102978 1000 concurrent users]
* [http://moodle.org/mod/forum/discuss.php?d=103040 Tool to estimate server's maximum concurrent users]

===What are the requirements for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

This is another way of asking the same question as above. Please move up.

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-10T09:08:15Z

Ratna: /* My site is very slow, what should I do? consistant links */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] fourm, the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something (see Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency]). It may by processing a webpage written in PHP, querrying the database or simply transfering a file.

===How do I benchmark a Moodle-site?===
You can of course benchmark each component of the software stack: operating system, webserver, database server, PHP (see [[Performance#Obtain_a_baseline_benchmark]]). But there is no easy formula to deduct the maximum number of concurrent users from those results.

There is a PHP-script, the [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script], circulating amoung the Moodle-community which calculates a ballpark figure. The current version is attached to the [http://moodle.org/mod/forum/discuss.php?d=57028#p296907 posting on 1. March 2007].

Warning: Note that running this script on a production server may have unwanted side-effects. You are strongly adviced to run it on a test-site.

===What are PHP-accelerators?===
See Wikipedia article [http://en.wikipedia.org/wiki/PHP_accelerator PHP accelerator].

Available software are documented [[Performance#PHP_performance]].

===How do I cluster Moodle?===

See [[Performance#Scalability]]

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [[Performance#Performance of different Moodle modules]]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[[Performance#Obtain a baseline benchmark]] and compare it with the published figures.

See also:
* [http://moodle.org/mod/forum/discuss.php?d=102978 1000 concurrent users]
* [http://moodle.org/mod/forum/discuss.php?d=103040 Tool to estimate server's maximum concurrent users]

===What are the requirements for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_are_the_requirements_for_N_users.3F What are the requirements for N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-10T09:04:04Z

Ratna: /* My site is very slow, what should I do? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] fourm, the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something (see Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency]). It may by processing a webpage written in PHP, querrying the database or simply transfering a file.

===How do I benchmark a Moodle-site?===
You can of course benchmark each component of the software stack: operating system, webserver, database server, PHP (see [[Performance#Obtain_a_baseline_benchmark]]). But there is no easy formula to deduct the maximum number of concurrent users from those results.

There is a PHP-script, the [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script], circulating amoung the Moodle-community which calculates a ballpark figure. The current version is attached to the [http://moodle.org/mod/forum/discuss.php?d=57028#p296907 posting on 1. March 2007].

Warning: Note that running this script on a production server may have unwanted side-effects. You are strongly adviced to run it on a test-site.

===What are PHP-accelerators?===
See Wikipedia article [http://en.wikipedia.org/wiki/PHP_accelerator PHP accelerator].

Available software are documented [[Performance#PHP_performance]].

===How do I cluster Moodle?===

See [[Performance#Scalability]]

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[[Performance#Obtain a baseline benchmark]] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What are the requirements for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_are_the_requirements_for_N_users.3F What are the requirements for N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-10T09:01:35Z

Ratna: /* How do I cluster Moodle? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] fourm, the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something (see Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency]). It may by processing a webpage written in PHP, querrying the database or simply transfering a file.

===How do I benchmark a Moodle-site?===
You can of course benchmark each component of the software stack: operating system, webserver, database server, PHP (see [[Performance#Obtain_a_baseline_benchmark]]). But there is no easy formula to deduct the maximum number of concurrent users from those results.

There is a PHP-script, the [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script], circulating amoung the Moodle-community which calculates a ballpark figure. The current version is attached to the [http://moodle.org/mod/forum/discuss.php?d=57028#p296907 posting on 1. March 2007].

Warning: Note that running this script on a production server may have unwanted side-effects. You are strongly adviced to run it on a test-site.

===What are PHP-accelerators?===
See Wikipedia article [http://en.wikipedia.org/wiki/PHP_accelerator PHP accelerator].

Available software are documented [[Performance#PHP_performance]].

===How do I cluster Moodle?===

See [[Performance#Scalability]]

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What are the requirements for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_are_the_requirements_for_N_users.3F What are the requirements for N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Administrator documentation

2009-10-10T08:56:49Z

Ratna: /* FAQs, added Performance FAQ */

The purpose of this page is to list useful links by general topics for administrators of a Moodle site.
__TOC__

== Installation & Upgrading ==

*[[Installation Quickstart]] for an overview of the installation steps
*[[Installing Moodle]] for detailed installation instructions
*[[Installation FAQ]]
*[[Installing AMP|Options for installing Apache, MySQL and PHP]]
*[[Upgrading|Upgrading Moodle]]
*[[Installing contributed modules or plugins]]

== System-specific Instructions & Packages ==

===Unix/Linux-based===
* [[SUSE Linux Server 10|Automated Installation Guide for SUSE Linux Enterprise Server 10]] operating system
* [[RedHat Linux installation|Step-by-step Installation Guide for RedHat]] operating system
* [[Debian GNU/Linux installation|Step-by-step Installation Guide for Debian GNU/Linux]] operating system
* [[Step-by-step Install Guide for Ubuntu]]
* [[Step-by-step Install Guide for Ubuntu using apt-get]]
* [[Step-by-step Install Guide for Zenwalk-5.0]]
* [[OLPC XS installation|Step-by-step Installation Guide for the One Laptop per Child XS Server (Beta)]]
* [[Step-by-step Install Guide for Solaris 10 with Oracle 10]]

===Windows===
* [[Windows installation|Windows installations with instructions for Windows NT/2000/2003 servers]]
* [[Windows installation using XAMPP|Windows installation using XAMPP: Apache, MySQL and PHP]]
* [[Development:Windows_Installer_anywhere|MoodleAnywhere]] another Windows installation package
* [[Installing Moodle on Windows Vista]] - how to

===Mac===
* [[Complete Install Packages for Mac OS X | Complete Install Packages for Mac OS X 10.3/10.4/10.5]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client|Step by Step Installation on a Mac OS X 10.4 Client using the internal web server]]
* [[Step by Step Installation on a Mac OS X 10.5 Server|Step by step Installation on a Mac OS X 10.5 Server]]

===Web Hosts===
* [[1and1_MySQL_installation | Installation on '''1and1''' web hosting]]
* [[powweb_MySQL_installation | Step-by-step Installation on '''Powweb''' web hosting]]

===Database===
* [[Installing Oracle for PHP]]
* [[Installing MSSQL for PHP]]
* [[Installing Postgres for PHP]]

==Security, Performance and Roles==

*[[Security]] contains important security procedures for a production site
*[[Performance]] for ideas on improving the speed of your installation
*[[Manage roles]] For Moodle 1.7 and later.
*[[Reducing spam in Moodle]]
*[[suhosin]] is an advanced protection system for PHP installation. It was designed to protect servers and users from known and unknown flaws in PHP applications and the PHP core.

== FAQs ==

*[[Installation FAQ]]
*[[Beginning Administration FAQ]]
*[[Administration FAQ]]
*[[Performance FAQ]]
*[[Backup and restore FAQ]]
*[[Errors FAQ]]

== Configuration Settings ==
*[[Site administration block]] contains configuration setting links
*[[Notification page]] used to update versions
*[[Variables]]
*[[Site settings]]
*[[Themes]]
*[[Language]]
*[[Activity modules administration]]
*[[Blocks administration]]
*[[Filters]]
*[[Backup settings]]
*[[HTML editor settings]]
*[[Calendar settings]]
*[[Maintenance mode]]

* See also:
**[[Location of admin settings in 1.7|Comparison between configuration settings in Moodle 1.6 & 1.7]]

==User Management==

*[[Authentication]]
*[[Add new user|Add a new user]] - on a site
*[[Upload users]] - from a file to a site, and into existing course and group, some existing user global updates
*[[User_profile_fields]]
*[[Enrolment plugins]]
**[[Flat file]] - enrol existing users in a course
*[[Roles and capabilities|Assigning user a role]] - typical assignments include:
**[[Students|Enrol students in a course]]
**[[Unenrolment]] Student
**[[Courses (administrator)|Assign teachers]] - to a course
**[[Assign creators|Assign course creators]] - in a site
**[[Assign administrators]] - in a site

==Other==

*[[Courses (administrator)|Courses]] and [[Course formats|course formats]]
*[[Reports (administrator)]] and [[Logs]]
*[[Site files]]
*[[Moodle database|Database]]
*[[Environment]]
*[[Moodle Network]] and Moodle [[Community hub]]
*[[Streaming Media]]
*[[Case studies (administrator)]]
*[[Anti-virus]]
*[[System Monitoring and Server Statistic Software]]
*[[Integrate Moodle, LDAP and SIMS.net]]
*[[How to rebuild context paths]]
*[[Hacking the Moodle 2.0 database transfer script to convert a Moodle 1.9 site]]
*[[Category:ProxyProblems]]

==See also==

*[[:Category:Administrator | Index of all Administrator-related pages]]
*[[Integrations]]
*[[CVS for Administrators]]
*[[Email processing]]
*[[Search engine optimization]]
*[[Messaging]]
*[[Migration]]
*[[Metacourses]]
*[[Block layout]]
*[[Customizing Moodle]]
*[[Administrator do's and don'ts]]
*[[Using Moodle book]] Chapter 16: Moodle Administration
*[[Administration hacks]]

[[Category: Administrator]]
[[cs:Rukověť správce]]
[[es:Documentación para Administradores]]
[[eu:Kudeatzaileentzako dokumentazioa]]
[[fr:Documentation administrateur]]
[[ja:管理者ドキュメント]]
[[ko:관리자 문서]]
[[nl:Documentatie voor beheerders]]
[[pt:Documentação para administradores]]
[[ru:Администраторам]]
[[sk:Dokumentácia pre správcov]]
[[zh:管理员文档]]
[[pl:Administrator documentation]]
[[fi:Ylläpitäjän opas]]
[[de:Dokumentation für Administratoren]]

Performance recommendations

2009-10-10T08:56:02Z

Ratna: /* See also */

Location: ''Administration > Server > Performance''

Moodle can be made to perform very well, at small usage levels or scaling up to many thousands of users. The factors involved in performance are basically the same as for any PHP-based database-driven system. When trying to optimize your server, try to focus on the factor which will make the most difference to the user. For example, if you have relatively more users browsing than accessing the database, look to improve the webserver performance.

==Obtain a baseline benchmark==

Before attempting any optimization, you should obtain a baseline benchmark of the component of the system you are trying to improve. For Linux try [http://lbs.sourceforge.net/ LBS] and for Windows use the Performance Monitor. Once you have quantitative data about how your system is performing currently, you'll be able to determine if the change you have made as has any real impact.

The overall aim of adjustments to improve performance is to use RAM (cacheing) and to reduce disk-based activity. It is especially important to try to eliminate swap file usage as much as you can. If your system starts swapping, this is a sign that you need more RAM.

The '''optimization order preference''' is usually: primary storage (more RAM), secondary storage (faster hard disks/improved hard disk configuration), processor (more and faster).

==Scalability==

Moodle's design (with clear separation of application layers) allows for strongly scalable setups. (Please check the list of [[Large installations|large Moodle installations]].)

Large sites usually separate the web server and database onto separate servers, although for smaller installations this is typically not necessary.

It is possible to load-balance a Moodle installation, for example by using more than one webserver. The separate webservers should query the same database and refer to the same filestore area, but otherwise the separation of the application layers is complete enough to make this kind of clustering feasible. Similarly, the database could be a cluster of servers (e.g. a MySQL cluster), but this is not an easy task and you should seek expert support, e.g. from a Moodle Partner.

'''See also''':
*[[Server cluster]]
*[http://moodle.org/mod/forum/discuss.php?d=4801 Scalability] forum discussion.
*[http://moodle.org/mod/forum/discuss.php?d=57202 Moodle clustering] forum discussion.
*[http://moodle.org/mod/forum/discuss.php?d=44470 Software load balancing] forum discussion.
*[http://moodle.org/mod/forum/discuss.php?d=49986 TCP load balancing] forum dicsussion.

==Hardware configuration==
'''Note''': The fastest and most effective change that you can make to improve performance is to '''increase the amount of RAM on your web server''' - get as much as possible (eg 4GB). Increasing primary memory will reduce the need for processes to swap to disk and will enable your server to handle more users.
* Better performance is gained by obtaining the best '''processor capability''' you can, i.e. dual or dual core processors. A modern BIOS should allow you to enable hyperthreading, but check if this makes a difference to the overall performance of the processors by using a [http://en.wikipedia.org/wiki/Super_PI CPU benchmarking tool].
* If you can afford them, use '''SCSI hard disks''' instead of SATA drives. SATA drives will increase your system's CPU utilization, whereas SCSI drives have their own integrated processors and come into their own when you have multiple drives. If you must have SATA drives, check that your motherboard and the drives themselves support NCQ (Native Command Queuing).
* Purchase hard disks with a '''low seek time'''. This will improve the overall speed of your system, especially when accessing Moodle's reports.
* Size your '''swap file''' correctly. The general advice is to set it to 4 x physical RAM.
* Use a '''RAID disk system'''. Although there are many different RAID configurations you can create, the following generally works best:
** install a hardware RAID controller (if you can)
** the operating system and swap drive on one set of disks configured as RAID-1.
** Moodle, Web server and Database server on another set of disks configured as RAID-5.
* Use '''gigabit ethernet''' for improved latency and throughput. This is especially important when you have your webserver and database server separated out on different hosts.
* Check the settings on your '''network card'''. You may get an improvement in performance by increasing the use of buffers and transmit/receive descriptors (balance this with processor and memory overheads) and off-loading TCP checksum calculation onto the card instead of the OS.
* Read this [http://moodle.org/mod/forum/discuss.php?d=68579 Case Study] on a server stress test with 300 users.
* See this [http://elearning.sgu.ac.jp/doc/PT/ accompanying report] on network traffic and server loads.
* See the [[Moodle.org configuration]]
* Also see this SFSU presentation at Educause (using VMWare): [http://www.educause.edu/Resources/AnOpenSourceLMSforaMissionCrit/162843]

==Operating System==
* You can use [http://en.wikipedia.org/wiki/Linux Linux](recommended), Unix-based, Windows or Mac OS X for the server '''operating system'''. *nix operating systems generally require less memory than Mac OS X or Windows servers for doing the same task as the server is configured with just a shell interface. Additionally Linux does not have licensing fees attached, but can have a big learning curve if you're used to another operating system. If you have a large number of processors running SMP, you may also want to consider using a highly tuned OS such as [http://en.wikipedia.org/wiki/Solaris_Operating_Environment Solaris].
* Check your own OS and '''vendor specific instructions''' for optimization steps.
** For Linux look at the [http://linuxperf.sourceforge.net/ Linux Performance Team] site.
** For Linux investigate the hdparm command, e.g. hdparm -m16 -d1 can be used to enable read/write on multiple sectors and DMA. Mount disks with the async and noatime options.
** For Windows set the sever to be optimized for network applications (Control Panel, Network Connections, LAN connection, Properties, File & Printer Sharing for Microsoft Networks, Properties, Optimization). You can also search the [http://technet.microsoft.com/ Microsoft TechNet site] for optimization documents.

==Web server performance==

Installing [http://www.mozilla.com/en-US/ Firefox] and the [https://addons.mozilla.org/en-US/firefox/addon/1843 firebug] extension will allow you to watch the time it takes for each page component to load. Also, the [https://addons.mozilla.org/en-US/firefox/addon/5369 Yslow] extension will evaluate your page against Yahoo's [http://www.skrenta.com/2007/05/14_rules_for_fast_web_pages_by_1.html 14 rules] ([http://video.yahoo.com/video/play?vid=1040890 video]) for fast loading websites.

===PHP performance===
* You are strongly recommended to use a '''PHP accelerator''' to ease CPU load, such as [http://pecl.php.net/apc APC], [http://www.php-accelerator.co.uk/ PHPA], [http://trac.lighttpd.net/xcache/ Xcache] or [http://eaccelerator.net/ eAccelerator]. (Take care to choose a PHP accelerator that is known to work well with your version of PHP and note that Turck MMCache is [http://turckmmcache.exeprod.com/TheManifestoEnglish no longer maintained] and can cause failures with PHP 5).
* Improvements in read/write performance can be improved by putting the cached PHP pages on a [[TMPFS]] filesystem - but remember that you'll lose the cache contents when there is a power failure or the server is rebooted.
* Performance of PHP is better when installed as an '''Apache/IIS ISAPI module''' (rather than a CGI).
* Also check the '''memory_limit''' in php.ini, reduce it to 16M for Moodle version earlier than 1.7 ([http://moodle.org/mod/forum/discuss.php?d=39656 See this forum discussion]). For Moodle 1.7 or later, it is recommended that the value of memory_limit should be 40M. As of [http://www.php.net/ChangeLog-5.php PHP 5.2.1] the default value for the memory_limit directive is 128M.

===Apache performance===
* If you are using Apache on a Windows server, use the build from [http://www.apachelounge.com Apache Lounge] which is reported to have [http://moodle.org/mod/forum/discuss.php?d=93358 performance and stability improvements] compared to the official Apache download. Note that this is an unofficial build, so may not keep up with official releases.
* Set the '''MaxClients''' directive correctly. Use this formula to help (which uses 80% of available memory to leave room for spare):
MaxClients = Total available memory * 80% / Max memory usage of apache process
:Memory usage of apache process is usually 10MB, so a general rule of thumb is to divide your available memory in megabytes by 10 to get the value of MaxClients. To find the max memory usage of apache processes read the value from the shell command:
#ps -ylC httpd --sort:rss

:If you need to increase the value of '''MaxClients''' beyond 256, you will also need to set the '''ServerLimit''' directive.

:'''Warning''': Do not be tempted to set the value of MaxClients higher than your available memory as your server will consume more RAM than available and start to swap to disk.
* Consider reducing the '''number of modules''' that Apache loads in the httpd.conf file to the minumum necessary to reduce the memory needed.
* Use the '''latest version of Apache''' - Apache 2 has an improved memory model which reduces memory usage further.
* For Unix/Linux systems, consider lowering '''MaxRequestsPerChild''' in httpd.conf to as low as 20-30 (if you set it any lower the overhead of forking begins to outweigh the benefits).
* For a heavily loaded server, consider setting '''KeepAlive Off''' (do this only if your Moodle pages do not contain links to resources or uploaded images) or lowering the '''KeepAliveTimeout''' to between 2 and 5. The default is 15 (seconds) - the higher the value the more server processes will be kept waiting for possibly idle connections. A more accurate value for KeepAliveTimeout is obtained by observing how long it takes your users to download a page. After altering any of the KeepAlive variables, monitor your CPU utilization as there may be an additional overhead in initiating more worker processes/threads.
* A warning about the previous performance tip. Microsoft Internet Explorer has a (little) known bug that causes seriously problems with SSL-enabled Apache websites. The issue is that if a web server's KeepAlive timeout is set to less than 60 seconds (say to the default of 15 seconds), MSIE can get confused about whether a keep-alive connection is available or not. As a result, any browser POST requests (which always use a keep-alive if available) will fail to reach the server. This is easily reproduced with postings to the Moodle forums. Using MSIE, connect to an ssl-enabled Moodle site. Write a quick forum post, and submit it when the form has been displayed for between 15 seconds and 60 seconds. You will see a browser error message, and your post content will be lost. In some cases, doing this will even crash the Windows TCP stack on the client machine. ''' So, if your site is SSL-enabled, and you use Apache, you should set the KeepAliveTimeout to at least 60 seconds'''.
* As an alternative to using KeepAlive Off, consider setting-up a '''Reverse Proxy server''' infront of the Moodle server to cache HTML files with images. You can then return Apache to using keep-alives on the Moodle server.
* If you do not use a .htaccess file, set the '''AllowOverride''' variable to AllowOverride None to prevent .htaccess lookups.
* Set '''DirectoryIndex''' correctly so as to avoid content-negotiation. Here's an example from a production server:
DirectoryIndex index.php index.html index.htm
* Unless you are doing development work on the server, set '''ExtendedStatus Off''' and disable mod_info as well as mod_status.
* Leave '''HostnameLookups Off''' (as default) to reduce DNS latency.
* Consider reducing the value of '''TimeOut''' to between 30 to 60 (seconds).
* For the '''Options directive''', avoid Options Multiviews as this performs a directory scan. To reduce disk I/O further use
Options -Indexes FollowSymLinks
*'''Caching''' - Apache can be told to make pages load a lot faster by specifying that the browser should cache some various page elements such as images and reuse them from local memory rather than ask for them again every time a page is requested. How to do this varies slightly between OSes but there are two basic steps:

# Install and enable mod_expires - refer to documentation or man pages
# Add this code to the virtual server config file within the <directory> section for the root directory (or within the .htaccess file if AllowOverrides is On):
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 1 seconds"
ExpiresByType text/html "access plus 1 seconds"
ExpiresByType image/gif "access plus 1 week"
ExpiresByType image/jpeg "access plus 1 week"
ExpiresByType image/png "access plus 1 week"
ExpiresByType text/css "access plus 1 week"
ExpiresByType text/javascript "access plus 1 week"
ExpiresByType application/x-javascript "access plus 1 week"
ExpiresByType text/xml "access plus 1 seconds"
</IfModule>

The effect is to make everything stay in the cache except HTML and XML, which change dynamically. It's possible to gain a several hundred percent decrease in load times this way. Adjust the cache times according to how often your images etc change.

More info: [http://www.metaskills.net/blog/heuristics/sysadmin/how-to-control-browser-caching-with-apache-2 www.metaskills.net]

===IIS performance===
All alter this location in the registry:
HKLM\SYSTEM\CurrentControlSet\Services\Inetinfo\Parameters\
* The equivalent to KeepAliveTimeout is '''ListenBackLog''' (IIS - registry location is HKLM\ SYSTEM\ CurrentControlSet\ Services\ Inetinfo\ Parameters). Set this to between 2 to 5.
*Change the '''MemCacheSize''' value to adjust the amount of memory (Mb) that IIS will use for its file cache (50% of available memory by default).
*Change the '''MaxCachedFileSize''' to adjust the maximum size of a file cached in the file cache in bytes. Default is 262,144 (256K).
*Create a new DWORD called '''ObjectCacheTTL''' to change the length of time (in milliseconds) that objects in the cache are held in memory. Default is 30,000 milliseconds (30 seconds).

===Lighttpd performance===
You can increase server performance by using a '''light-weight''' webserver like [http://www.lighttpd.net/ lighttpd] (or [http://nginx.net/ nginx])in combination with PHP in FastCGI-mode. Lighttpd was originally created as a proof-of-concept[http://www.lighttpd.net/story] to address the [http://www.kegel.com/c10k.html C10k problem] and while primarily recommended for memory-limited servers, its design origins and asynchronous-IO model make it a suitable and proven[http://blog.lighttpd.net/articles/2006/12/28/lighttpd-powers-5-alexa-top-250-sites] alternative HTTP server for high-load websites and web apps, including Moodle. See the [[lighttpd | MoodleDocs Lighttpd page]] for additional information, configuration example and links.

Alternatively, both [http://www.lighttpd.net/ lighttpd] and [http://nginx.net/ nginx] are capable of performing as a load-balancer and/or reverse-proxy to alleviate load on back-end servers[http://www.linuxjournal.com/article/10108], providing benefit without requiring an actual software change on existing servers.

==Database performance==

Moodle contains a script which will display some key database performance statistics from the [http://phplens.com/lens/adodb/docs-perf.htm ADOdb performance monitor]. Run the script in your browser as in the following example:

http://www.mymoodle.com/admin/dbperformance.php

Use the data displayed as a guide to tune and improve the performance of your database server.

===MySQL performance===

The following are MySQL specific settings which can be adjusted for better performance in your my.cnf (my.ini in Windows). The file contains a list of settings and their values. To see the current values use these commands
SHOW STATUS;
SHOW VARIABLES;
'''Important''': You must make backups of your database before attempting to change any MySQL server configuration. After any change to the my.cnf, restart mysqld.

If you are able, the [http://wiki.mysqltuner.com/MySQLTuner MySQLTuner] tool can be run against your MySQL server and will calculate appropriate configuration values for most of the following settings based on your current load, status and variables automatically.

* Enable the '''query cache''' with
query_cache_type = 1.
For most Moodle installs, set the following:
query_cache_size = 36M
query_cache_min_res_unit = 2K.
The query cache will improve performance if you are doing few updates on the database.
* Set the '''table cache''' correctly. For Moodle 1.6 set
table_cache = 256 #(table_open_cache in MySQL > 5.1.2)
(min), and for Moodle 1.7 set
table_cache = 512 #(table_open_cache in MySQL > 5.1.2)
(min). The table cache is used by all threads (connections), so monitor the value of opened_tables to further adjust - if opened_tables > 3 * table_cache(table_open_cache in MySQL > 5.1.2) then increase table_cache upto your OS limit. Note also that the figure for table_cache will also change depending on the number of modules and plugins you have installed. Find the number for your server by executing the mysql statement below. Look at the number returned and set table_cache to this value.
mysql>SELECT COUNT(table_name) FROM information_schema.tables WHERE table_schema='yourmoodledbname';
* Set the '''thread cache''' correctly. Adjust the value so that your thread cache utilization is as close to 100% as possible by this formula:
thread cache utilization (%) = (threads_created / connections) * 100
* The '''key buffer''' can improve the access speed to Moodle's SELECT queries. The correct size depends on the size of the index files (.myi) and in Moodle 1.6 or later (without any additional modules and plugins), the recommendation for this value is key_buffer_size = 32M. Ideally you want the database to be reading once from the disk for every 100 requests so monitor that the value is suitable for your install by adjusting the value of key_buffer_size so that the following formulas are true:
key_read / key_read_requests < 0.01
key_write / key_write_requests <= 1.0
* Set the '''maximum number of connections''' so that your users will not see a "Too many connections" message. Be careful that this may have an impact on the total memory used. MySQL connections usually last for milliseconds, so it is unusual even for a heavily loaded server for this value to be over 200.
* Manage '''high burst activity'''. If your Moodle install uses a lot of quizzes and you are experiencing performance problems (check by monitoring the value of threads_connected - it should not be rising) consider increasing the value of back_log.
* '''Optimize your tables weekly and after upgrading Moodle'''. It is good practice to also optimize your tables after performing a large data deletion exercise, e.g. at the end of your semester or academic year. This will ensure that index files are up to date. Backup your database first and then use:
mysql>CHECK TABLE mdl_tablename;
mysql>OPTIMIZE TABLE mdl_tablename;
:The common tables in Moodle to check are mdl_course_sections, mdl_forum_posts, mdl_log and mdl_sessions (if using dbsessions). Any errors need to be corrected using REPAIR TABLE (see the [http://dev.mysql.com/doc/refman/5.0/en/repair-table.html MySQL manual] and this [http://moodle.org/mod/forum/discuss.php?d=58208#p279638 forum script]).
* '''Maintain the key distribution'''. Every month or so it is a good idea to stop the mysql server and run these myisamchk commands.
#myisamchk -a -S /pathtomysql/data/moodledir/*.MYI
:'''Warning''': You must stop the mysql database process (mysqld) before running any myisamchk command. If you do not, you risk data loss.
* Reduce the number of '''temporary tables saved to disk'''. Check this with the created_tmp_disk_tables value. If this is relatively large (>5%) increase tmp_table_size until you see a reduction. Note that this will have an impact on RAM usage.
* Moodle's tables are in the MyISAM format, so '''turn InnoDB off''' if you feel there is no performance gain. Add <code>skip-innodb</code> to your <code>my.cnf</code> file. If you must use InnoDB, you'll have to convert all of Moodle's tables. To do this run the innodb script:

http://www.mymoodle.com/admin/innodb.php

:See also [http://moodle.org/mod/forum/discuss.php?d=12961 this forum discussion] which looks at the MyISAM vs InnoDB options.

===PostgreSQL performance===

There are some good papers around on tuning PostgreSQL, and Moodle's case does not seem to be different to the general case.

The first thing to recognise is that if you really need to worry about tuning you should be using a separate machine for the database server. If you are not using a separate machine then the answers to many performance questions are substantially muddied by the memory requirements of the rest of the application.

You should probably '''enable autovacuum''', unless you know what you are doing. Many e-learning sites have predictable periods of low use, so disabling autovacuum and running a specific vacuum at those times can be a good option. Or perhaps leave autovacuum running but do a full vacuum weekly in a quiet period.

Set '''shared_buffers''' to something reasonable. For versions up to 8.1 my testing has shown that peak performance is almost always obtained with buffers < 10000, so if you are using such a version, and have more than 512M of RAM just set shared_buffers to 10,000 (8MB).

The buffer management had a big overhaul in 8.2 and "reasonable" is now a much larger number. I have not conducted performance tests with 8.2, but the recommendations from others are generally that you should now scale shared_buffers much more with memory and may continue to reap benefits even up to values like 100,000 (80MB). Consider using 1-2% of system RAM.

PostgreSQL will also assume that the operating system is caching its files, so setting '''effective_cache_size''' to a reasonable value is also a good idea. A reasonable value will usually be (total RAM - RAM in use by programs). If you are running Linux and leave the system running for a day or two you can look at 'free' and under the 'cached' column you will see what it currently is. Consider taking that number (which is kB) and dividing it by 10 (i.e. allow 20% for other programs cache needs and then divide by 8 to get pages). If you are not using a dedicated database server you will need to decrease that value to account for usage by other programs.

Some other useful parameters that can have positive effects, and the values I would typically set them to on a machine with 4G RAM, are:

work_mem = 10240

That's 10M of RAM to use instead of on-disk sorting and so forth. That can give a big speed increase, but it is per connection and 200 connections * 10M is 2G, so it can theoretically chew up a lot of RAM.

maintenance_work_mem = 163840

That's 160M of RAM which will be used by (e.g.) VACUUM, index rebuild, cluster and so forth. This should only be used periodically and should be freed when those processes exit, so I believe it is well worth while.

max_fsm_pages = 100000
max_fsm_relations = 5000

These are used to hold the free-space map, and if they are too small you will see performance degradation after the database has been operating for some time. The exact numbers to set can be gleaned from the output of VACUUM VERBOSE, which prints the required FSM pages at the end of it's run. The 5x increase seems to be useful for a Moodle installation, from experience.

wal_buffers = 64

These buffers are used for the write-ahead log, and there have been a number of reports on the PostgreSQL mailing lists of improvement from this level of increase.

This is a little out of date now (version 8.0) but still worth a read: http://www.powerpostgresql.com/Docs

And there is lots of good stuff here as well: http://www.varlena.com/varlena/GeneralBits/Tidbits/index.php

''Based on Andrew McMillan's post at [http://moodle.org/mod/forum/discuss.php?d=68558 Tuning PostgreSQL] forum thread.''

===Other database performance links===
* Consider using a '''distributed cacheing system''' like [http://en.wikipedia.org/wiki/Memcached memcached] but note that memcached does not have any security features so it should be used behind a firewall.
* Consider using PostgreSQL. See [[Arguments in favour of PostgreSQL]] and [http://moodle.org/mod/forum/discuss.php?d=49195 how to migrate from MySQL to PostgreSQL] (forum discussion).
* [[Increasing the database connection lifetime | Try increasing the database connection lifetime]]
* [http://dev.mysql.com/doc/refman/5.0/en/server-parameters.html General advice on tuning MySQL parameters] (advice from the MySQL manual)
* [http://www.mysqlperformanceblog.com/2007/11/01/innodb-performance-optimization-basics/ InnoDB performance optimization] taken from the [http://www.mysqlperformanceblog.com/ MySQL performance blog] site.

==Moodle Admin settings==
* In Moodle 1.7 or later, set the '''Cache type''' for your server: Site Admin -> Server -> Performance -> Cache type. There are several options available.
:*If you do not have eaccelerator or mmemcached installed, choose "internal" (which makes use of the record/internal cache - see the next bullet point).
:* If you have a single server and have compiled '''eaccelerator with shared memory support''', set the cache type to the eaccelerator option.
:* If you have a '''separate memcached server''', set the cache type to memcached and enter a csv list of server IP addresses.
* Enable the '''record/internal cache''': Site Admin -> Server -> Performance -> Record cache = True. Set the maximum amount of memory allocated to the cache in the Int Cache Max box. This will enable a primary cache for database records, without using any database engine cache, e.g. MySQL/PostgreSQL cache. See [http://tracker.moodle.org/browse/MDL-7196 this Tracker entry] for a full discussion.
* Enable the '''language cache'''.
* Large log files can cause overall performance to degrade over time. If you observe that the site has gradually got slower loading pages in the browser, '''reduce your Log life time''' setting (Admin/Server/Cleanup).
* Performance can be greatly improved by allowing Moodle to use the system '''zip/unzip''' commands (rather than PHP-based zip libraries) - visit Admin/Server/System Paths and enter the path to the relevant executables. (Similarly, filling in the path to '''du''' will improve Moodle's speed at listing directory contents.)
* Note that using '''secure web connections''' ('''https''' rather than '''http''') carries a higher processing burden, both for the webserver and the client - particularly because cacheing cannot be used as effectively, so the number of file requests is likely to increase dramatically. For this reason using https for all Moodle pages is not recommended. You can enable https just for the login screen, simply from Moodle's config page.
* Check your '''filters'''. Having too many filters active can have serious effects on server load, especially on lower-end systems. The number of active filters has a direct effect on the perceived latency of your site; that is the time taken for each page impression.
* Enable the '''text cache''' but do not "Filter all strings" unless you have a specific need. If in doubt profile the performance, and see how your changes affect the processing time.
* Check your '''anti-virus''' measures on the server. Although they are useful for preventing security holes being exploited, some "On-Demand" scanners can affect performance by scanning page content (word, ppt files etc).
* If there are performance problems loading course pages, check the '''Resource module settings'''. The setting resource_filterexternalpages is known to slow-down course pages and should be set to 'No' for better performance.
* Check your '''forum settings'''. To improve performance set forum_trackreadposts = No and forum_usermarksread = Yes (this will impact on the convenience of your users' forum experience). Also consider setting the time of the day when old posts are cleared from the read table (forum_cleanreadtime) to when your site is less busy.

==Performance of different Moodle modules==

Moodle's activity modules, filters, and other plugins can be activated/deactivated. If necessary, you may wish to deactivate some features (such as chat) if not required - but this isn't necessary. Some notes on the performance of certain modules:

* The '''Chat''' module is [http://moodle.org/mod/forum/discuss.php?d=37979&parent=175079 said] to be a hog in terms of frequent HTTP requests to the main server. This can be reduced by setting the module to use ''Streamed'' updates, or, if you're using a Unix-based webserver, by running the chat in daemon mode. When using the Chat module use the configuration settings to tune for your expected load. Pay particular attention to the ''chat_old_ping'' and ''chat_refresh'' parameters as these can have greatest impact on server load.
* The '''Quiz''' module is known to stretch database performance. Try to optimise your database server by tuning. See [http://moodle.org/mod/forum/discuss.php?d=25616&parent=120770 for a brief report on performance for 55 students simultaneously using quizzes]
** See this Case Study for an extensive server stress test with 300 quiz users.[http://moodle.org/mod/forum/discuss.php?d=68579] And this accompanying report on network traffic and server loads. [http://elearning.sgu.ac.jp/doc/PT/]
* The Moodle '''Cron''' task is triggered by calling the script ''cron.php''. If this is called over HTTP (e.g. using wget or curl) it can take a large amount of memory on large installations. If it is called by directly invoking the php command (e.g. ''php -f /path/to/moodle/directory/admin/cron.php'') efficiency can be much improved.
* The '''Recent activities''' block is consuming to much resources if you have huge number of records <code>mdl_log</code>. this is being tested to optimize the SQL query.

==Moodle Image Optimization==

The base images delivered in the original Moodle distribution package provide unoptimized graphics, most of which can benefit from lossless recompression utilizing [http://optipng.sourceforge.net/ optipng] for PNGs, [http://www.lcdf.org/gifsicle/ gifsicle] for GIFs and [http://www.kokkonen.net/tjko/projects.html jpegoptim] for JPGs. Optimized graphics transfer faster and provide a faster perceived response for clients[http://www.websiteoptimization.com/speed/12/], especially distance learners. The following example will recursively optimize (without any loss of quality) all the graphics and image files included in a base Moodle installation directory on a server with the above commands installed and available.

<pre>
find /example/directory/moodle-1.9 -iname *.png -exec optipng -o7 {} \;
find /example/directory/moodle-1.9 -iname *.gif -exec gifsicle -O2 -b {} \;
find /example/directory/moodle-1.9 -iname *.jpg -exec jpegoptim -p {} \;
</pre>

Both [http://optipng.sourceforge.net/ optipng] and [http://www.lcdf.org/gifsicle/ gifsicle] are provided in the base repositories of most newer Linux distributions; [http://www.kokkonen.net/tjko/projects.html jpegoptim] must be downloaded and installed manually.

==See also==

*[[Performance FAQ]]
*Using Moodle: [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance] forum

There have been a lot of discussions on moodle.org about performance, here are some of the more interesting and (potentially) useful ones:

* [http://moodle.org/mod/forum/discuss.php?d=83057 Performance woes!]
* [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script]
* [http://moodle.org/mod/forum/discuss.php?d=88927 Comments on planned server hardware]
* [http://moodle.org/mod/forum/discuss.php?d=102978#p461624 Moodle performance in a pil by Martin Langhoff]
[[Category:Performance]]

[[fr:Performance]]
[[ja:パフォーマンス]]
[[pl:Wydajność]]

Administrator documentation

2009-10-10T08:47:05Z

Ratna: /* consistant link text in Security, Performance and Roles, no Top */

The purpose of this page is to list useful links by general topics for administrators of a Moodle site.
__TOC__

== Installation & Upgrading ==

*[[Installation Quickstart]] for an overview of the installation steps
*[[Installing Moodle]] for detailed installation instructions
*[[Installation FAQ]]
*[[Installing AMP|Options for installing Apache, MySQL and PHP]]
*[[Upgrading|Upgrading Moodle]]
*[[Installing contributed modules or plugins]]

== System-specific Instructions & Packages ==

===Unix/Linux-based===
* [[SUSE Linux Server 10|Automated Installation Guide for SUSE Linux Enterprise Server 10]] operating system
* [[RedHat Linux installation|Step-by-step Installation Guide for RedHat]] operating system
* [[Debian GNU/Linux installation|Step-by-step Installation Guide for Debian GNU/Linux]] operating system
* [[Step-by-step Install Guide for Ubuntu]]
* [[Step-by-step Install Guide for Ubuntu using apt-get]]
* [[Step-by-step Install Guide for Zenwalk-5.0]]
* [[OLPC XS installation|Step-by-step Installation Guide for the One Laptop per Child XS Server (Beta)]]
* [[Step-by-step Install Guide for Solaris 10 with Oracle 10]]

===Windows===
* [[Windows installation|Windows installations with instructions for Windows NT/2000/2003 servers]]
* [[Windows installation using XAMPP|Windows installation using XAMPP: Apache, MySQL and PHP]]
* [[Development:Windows_Installer_anywhere|MoodleAnywhere]] another Windows installation package
* [[Installing Moodle on Windows Vista]] - how to

===Mac===
* [[Complete Install Packages for Mac OS X | Complete Install Packages for Mac OS X 10.3/10.4/10.5]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client|Step by Step Installation on a Mac OS X 10.4 Client using the internal web server]]
* [[Step by Step Installation on a Mac OS X 10.5 Server|Step by step Installation on a Mac OS X 10.5 Server]]

===Web Hosts===
* [[1and1_MySQL_installation | Installation on '''1and1''' web hosting]]
* [[powweb_MySQL_installation | Step-by-step Installation on '''Powweb''' web hosting]]

===Database===
* [[Installing Oracle for PHP]]
* [[Installing MSSQL for PHP]]
* [[Installing Postgres for PHP]]

==Security, Performance and Roles==

*[[Security]] contains important security procedures for a production site
*[[Performance]] for ideas on improving the speed of your installation
*[[Manage roles]] For Moodle 1.7 and later.
*[[Reducing spam in Moodle]]
*[[suhosin]] is an advanced protection system for PHP installation. It was designed to protect servers and users from known and unknown flaws in PHP applications and the PHP core.

== FAQs ==

*[[Installation FAQ]]
*[[Beginning Administration FAQ]]
*[[Administration FAQ]]
*[[Backup and restore FAQ]]
*[[Errors FAQ]]

== Configuration Settings ==
*[[Site administration block]] contains configuration setting links
*[[Notification page]] used to update versions
*[[Variables]]
*[[Site settings]]
*[[Themes]]
*[[Language]]
*[[Activity modules administration]]
*[[Blocks administration]]
*[[Filters]]
*[[Backup settings]]
*[[HTML editor settings]]
*[[Calendar settings]]
*[[Maintenance mode]]

* See also:
**[[Location of admin settings in 1.7|Comparison between configuration settings in Moodle 1.6 & 1.7]]

==User Management==

*[[Authentication]]
*[[Add new user|Add a new user]] - on a site
*[[Upload users]] - from a file to a site, and into existing course and group, some existing user global updates
*[[User_profile_fields]]
*[[Enrolment plugins]]
**[[Flat file]] - enrol existing users in a course
*[[Roles and capabilities|Assigning user a role]] - typical assignments include:
**[[Students|Enrol students in a course]]
**[[Unenrolment]] Student
**[[Courses (administrator)|Assign teachers]] - to a course
**[[Assign creators|Assign course creators]] - in a site
**[[Assign administrators]] - in a site

==Other==

*[[Courses (administrator)|Courses]] and [[Course formats|course formats]]
*[[Reports (administrator)]] and [[Logs]]
*[[Site files]]
*[[Moodle database|Database]]
*[[Environment]]
*[[Moodle Network]] and Moodle [[Community hub]]
*[[Streaming Media]]
*[[Case studies (administrator)]]
*[[Anti-virus]]
*[[System Monitoring and Server Statistic Software]]
*[[Integrate Moodle, LDAP and SIMS.net]]
*[[How to rebuild context paths]]
*[[Hacking the Moodle 2.0 database transfer script to convert a Moodle 1.9 site]]
*[[Category:ProxyProblems]]

==See also==

*[[:Category:Administrator | Index of all Administrator-related pages]]
*[[Integrations]]
*[[CVS for Administrators]]
*[[Email processing]]
*[[Search engine optimization]]
*[[Messaging]]
*[[Migration]]
*[[Metacourses]]
*[[Block layout]]
*[[Customizing Moodle]]
*[[Administrator do's and don'ts]]
*[[Using Moodle book]] Chapter 16: Moodle Administration
*[[Administration hacks]]

[[Category: Administrator]]
[[cs:Rukověť správce]]
[[es:Documentación para Administradores]]
[[eu:Kudeatzaileentzako dokumentazioa]]
[[fr:Documentation administrateur]]
[[ja:管理者ドキュメント]]
[[ko:관리자 문서]]
[[nl:Documentatie voor beheerders]]
[[pt:Documentação para administradores]]
[[ru:Администраторам]]
[[sk:Dokumentácia pre správcov]]
[[zh:管理员文档]]
[[pl:Administrator documentation]]
[[fi:Ylläpitäjän opas]]
[[de:Dokumentation für Administratoren]]

Administrator documentation

2009-10-10T08:34:33Z

Ratna: removed "Table of Contents" as a section in itself

The purpose of this page is to list useful links by general topics for administrators of a Moodle site.
__TOC__

== Installation & Upgrading ==

*[[Installation Quickstart]] for an overview of the installation steps
*[[Installing Moodle]] for detailed installation instructions
*[[Installation FAQ]]
*[[Installing AMP|Options for installing Apache, MySQL and PHP]]
*[[Upgrading|Upgrading Moodle]]
*[[Installing contributed modules or plugins]]

== System-specific Instructions & Packages ==

===Unix/Linux-based===
* [[SUSE Linux Server 10|Automated Installation Guide for SUSE Linux Enterprise Server 10]] operating system
* [[RedHat Linux installation|Step-by-step Installation Guide for RedHat]] operating system
* [[Debian GNU/Linux installation|Step-by-step Installation Guide for Debian GNU/Linux]] operating system
* [[Step-by-step Install Guide for Ubuntu]]
* [[Step-by-step Install Guide for Ubuntu using apt-get]]
* [[Step-by-step Install Guide for Zenwalk-5.0]]
* [[OLPC XS installation|Step-by-step Installation Guide for the One Laptop per Child XS Server (Beta)]]
* [[Step-by-step Install Guide for Solaris 10 with Oracle 10]]

===Windows===
* [[Windows installation|Windows installations with instructions for Windows NT/2000/2003 servers]]
* [[Windows installation using XAMPP|Windows installation using XAMPP: Apache, MySQL and PHP]]
* [[Development:Windows_Installer_anywhere|MoodleAnywhere]] another Windows installation package
* [[Installing Moodle on Windows Vista]] - how to

===Mac===
* [[Complete Install Packages for Mac OS X | Complete Install Packages for Mac OS X 10.3/10.4/10.5]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client|Step by Step Installation on a Mac OS X 10.4 Client using the internal web server]]
* [[Step by Step Installation on a Mac OS X 10.5 Server|Step by step Installation on a Mac OS X 10.5 Server]]

===Web Hosts===
* [[1and1_MySQL_installation | Installation on '''1and1''' web hosting]]
* [[powweb_MySQL_installation | Step-by-step Installation on '''Powweb''' web hosting]]

===Database===
* [[Installing Oracle for PHP]]
* [[Installing MSSQL for PHP]]
* [[Installing Postgres for PHP]]

==Security, Performance and Roles==

*[[Security]] contains important security procedures for a production site
*[[Performance | Performance and optimization]] for ideas on improving the speed of your installation
*[[Manage roles | Managing roles]] For Moodle 1.7 and later.
*[[Reducing spam in Moodle]]
*[[suhosin]] is an advanced protection system for PHP installation. It was designed to protect servers and users from known and unknown flaws in PHP applications and the PHP core.

[[Administrator documentation#Table of Contents|Top]]
== FAQs ==

*[[Installation FAQ]]
*[[Beginning Administration FAQ]]
*[[Administration FAQ]]
*[[Backup and restore FAQ]]
*[[Errors FAQ]]

== Configuration Settings ==
*[[Site administration block]] contains configuration setting links
*[[Notification page]] used to update versions
*[[Variables]]
*[[Site settings]]
*[[Themes]]
*[[Language]]
*[[Activity modules administration]]
*[[Blocks administration]]
*[[Filters]]
*[[Backup settings]]
*[[HTML editor settings]]
*[[Calendar settings]]
*[[Maintenance mode]]

* See also:
**[[Location of admin settings in 1.7|Comparison between configuration settings in Moodle 1.6 & 1.7]]

==User Management==

*[[Authentication]]
*[[Add new user|Add a new user]] - on a site
*[[Upload users]] - from a file to a site, and into existing course and group, some existing user global updates
*[[User_profile_fields]]
*[[Enrolment plugins]]
**[[Flat file]] - enrol existing users in a course
*[[Roles and capabilities|Assigning user a role]] - typical assignments include:
**[[Students|Enrol students in a course]]
**[[Unenrolment]] Student
**[[Courses (administrator)|Assign teachers]] - to a course
**[[Assign creators|Assign course creators]] - in a site
**[[Assign administrators]] - in a site

==Other==

*[[Courses (administrator)|Courses]] and [[Course formats|course formats]]
*[[Reports (administrator)]] and [[Logs]]
*[[Site files]]
*[[Moodle database|Database]]
*[[Environment]]
*[[Moodle Network]] and Moodle [[Community hub]]
*[[Streaming Media]]
*[[Case studies (administrator)]]
*[[Anti-virus]]
*[[System Monitoring and Server Statistic Software]]
*[[Integrate Moodle, LDAP and SIMS.net]]
*[[How to rebuild context paths]]
*[[Hacking the Moodle 2.0 database transfer script to convert a Moodle 1.9 site]]
*[[Category:ProxyProblems]]

==See also==

*[[:Category:Administrator | Index of all Administrator-related pages]]
*[[Integrations]]
*[[CVS for Administrators]]
*[[Email processing]]
*[[Search engine optimization]]
*[[Messaging]]
*[[Migration]]
*[[Metacourses]]
*[[Block layout]]
*[[Customizing Moodle]]
*[[Administrator do's and don'ts]]
*[[Using Moodle book]] Chapter 16: Moodle Administration
*[[Administration hacks]]

[[Category: Administrator]]
[[cs:Rukověť správce]]
[[es:Documentación para Administradores]]
[[eu:Kudeatzaileentzako dokumentazioa]]
[[fr:Documentation administrateur]]
[[ja:管理者ドキュメント]]
[[ko:관리자 문서]]
[[nl:Documentatie voor beheerders]]
[[pt:Documentação para administradores]]
[[ru:Администраторам]]
[[sk:Dokumentácia pre správcov]]
[[zh:管理员文档]]
[[pl:Administrator documentation]]
[[fi:Ylläpitäjän opas]]
[[de:Dokumentation für Administratoren]]

Performance FAQ

2009-10-09T19:25:19Z

Ratna: /* What are PHP-accelerators? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] fourm, the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something (see Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency]). It may by processing a webpage written in PHP, querrying the database or simply transfering a file.

===How do I benchmark a Moodle-site?===
You can of course benchmark each component of the software stack: operating system, webserver, database server, PHP (see [[Performance#Obtain_a_baseline_benchmark]]). But there is no easy formula to deduct the maximum number of concurrent users from those results.

There is a PHP-script, the [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script], circulating amoung the Moodle-community which calculates a ballpark figure. The current version is attached to the [http://moodle.org/mod/forum/discuss.php?d=57028#p296907 posting on 1. March 2007].

Warning: Note that running this script on a production server may have unwanted side-effects. You are strongly adviced to run it on a test-site.

===What are PHP-accelerators?===
See Wikipedia article [http://en.wikipedia.org/wiki/PHP_accelerator PHP accelerator].

Available software are documented [[Performance#PHP_performance]].

===How do I cluster Moodle?===

http://moodle.org/mod/forum/discuss.php?d=57202

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What are the requirements for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_are_the_requirements_for_N_users.3F What are the requirements for N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-09T19:22:23Z

Ratna: /* How do I benchmark a Moodle-site? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] fourm, the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something (see Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency]). It may by processing a webpage written in PHP, querrying the database or simply transfering a file.

===How do I benchmark a Moodle-site?===
You can of course benchmark each component of the software stack: operating system, webserver, database server, PHP (see [[Performance#Obtain_a_baseline_benchmark]]). But there is no easy formula to deduct the maximum number of concurrent users from those results.

There is a PHP-script, the [http://moodle.org/mod/forum/discuss.php?d=57028 Performance perspectives - a little script], circulating amoung the Moodle-community which calculates a ballpark figure. The current version is attached to the [http://moodle.org/mod/forum/discuss.php?d=57028#p296907 posting on 1. March 2007].

Warning: Note that running this script on a production server may have unwanted side-effects. You are strongly adviced to run it on a test-site.

===What are PHP-accelerators?===
For the definition see Wikipedia [4]. Read the Performance documentation [5] for possible software.

[4] http://en.wikipedia.org/wiki/PHP_accelerator

[5] https://docs.moodle.org/en/Performance#PHP_performance

===How do I cluster Moodle?===

http://moodle.org/mod/forum/discuss.php?d=57202

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What are the requirements for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_are_the_requirements_for_N_users.3F What are the requirements for N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-09T19:14:48Z

Ratna:

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] fourm, the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something (see Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency]). It may by processing a webpage written in PHP, querrying the database or simply transfering a file.

===How do I benchmark a Moodle-site?===
You can ofcourse benchmark each component of the software stack, starting from the operating system upto the database https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark . But there is no easy formula to deduct the maximum number of concurrent users from those data.

There is a PHP-script [2] circulating amoung the Moodle-community which calculates a ballpark figure. Take the current version from 1. March 2007 posted here [3]. Please note running this script on a production server may have side-effects, you are strongly adviced to run it on a test-site.

[2] http://moodle.org/mod/forum/discuss.php?d=57028

[3] http://moodle.org/mod/forum/discuss.php?d=57028#p296907

===What are PHP-accelerators?===
For the definition see Wikipedia [4]. Read the Performance documentation [5] for possible software.

[4] http://en.wikipedia.org/wiki/PHP_accelerator

[5] https://docs.moodle.org/en/Performance#PHP_performance

===How do I cluster Moodle?===

http://moodle.org/mod/forum/discuss.php?d=57202

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What are the requirements for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_are_the_requirements_for_N_users.3F What are the requirements for N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-09T19:12:50Z

Ratna: /* How do you define "concurrent users"? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the [http://moodle.org/mod/forum/view.php?f=94 Hardware and performance] fourm, the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something (see Wikipedia [http://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency]). It may by processing a webpage written in PHP, querrying the database or simply transfering a file.

===How do I benchmark a Moodle-site?===
You can ofcourse benchmark each component of the software stack, starting from the operating system upto the database https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark . But there is no easy formula to deduct the maximum number of concurrent users from those data.

There is a PHP-script [2] circulating amoung the Moodle-community which calculates a ballpark figure. Take the current version from 1. March 2007 posted here [3]. Please note running this script on a production server may have side-effects, you are strongly adviced to run it on a test-site.

[2] http://moodle.org/mod/forum/discuss.php?d=57028

[3] http://moodle.org/mod/forum/discuss.php?d=57028#p296907

===What are PHP-accelerators?===
For the definition see Wikipedia [4]. Read the Performance documentation [5] for possible software.

[4] http://en.wikipedia.org/wiki/PHP_accelerator

[5] https://docs.moodle.org/en/Performance#PHP_performance

===How do I cluster Moodle?===

http://moodle.org/mod/forum/discuss.php?d=57202

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What are the requirments for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_are_the_requirments_for_N_users.3F What are the requirments for N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-09T19:08:03Z

Ratna: /* How many users will my installation support? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the forum [0], the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something [1]. It may by processing a webpage written in PHP, processing a database querry or simply transfering a file.

[0] Using Moodle [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance forum]

[1] http://en.wikipedia.org/wiki/Concurrency_(computer_science)

===How do I benchmark a Moodle-site?===
You can ofcourse benchmark each component of the software stack, starting from the operating system upto the database https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark . But there is no easy formula to deduct the maximum number of concurrent users from those data.

There is a PHP-script [2] circulating amoung the Moodle-community which calculates a ballpark figure. Take the current version from 1. March 2007 posted here [3]. Please note running this script on a production server may have side-effects, you are strongly adviced to run it on a test-site.

[2] http://moodle.org/mod/forum/discuss.php?d=57028

[3] http://moodle.org/mod/forum/discuss.php?d=57028#p296907

===What are PHP-accelerators?===
For the definition see Wikipedia [4]. Read the Performance documentation [5] for possible software.

[4] http://en.wikipedia.org/wiki/PHP_accelerator

[5] https://docs.moodle.org/en/Performance#PHP_performance

===How do I cluster Moodle?===

http://moodle.org/mod/forum/discuss.php?d=57202

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What are the requirments for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_are_the_requirments_for_N_users.3F What are the requirments for N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-09T19:06:39Z

Ratna: /* What hardware is needed for N users? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the forum [0], the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something [1]. It may by processing a webpage written in PHP, processing a database querry or simply transfering a file.

[0] Using Moodle [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance forum]

[1] http://en.wikipedia.org/wiki/Concurrency_(computer_science)

===How do I benchmark a Moodle-site?===
You can ofcourse benchmark each component of the software stack, starting from the operating system upto the database https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark . But there is no easy formula to deduct the maximum number of concurrent users from those data.

There is a PHP-script [2] circulating amoung the Moodle-community which calculates a ballpark figure. Take the current version from 1. March 2007 posted here [3]. Please note running this script on a production server may have side-effects, you are strongly adviced to run it on a test-site.

[2] http://moodle.org/mod/forum/discuss.php?d=57028

[3] http://moodle.org/mod/forum/discuss.php?d=57028#p296907

===What are PHP-accelerators?===
For the definition see Wikipedia [4]. Read the Performance documentation [5] for possible software.

[4] http://en.wikipedia.org/wiki/PHP_accelerator

[5] https://docs.moodle.org/en/Performance#PHP_performance

===How do I cluster Moodle?===

http://moodle.org/mod/forum/discuss.php?d=57202

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What are the requirments for N users?===

[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_hardware_is_needed_for_N_users.3F What hardware is needed for N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-09T15:07:28Z

Ratna: /* reomoved How do I setup multiple Moodle instances on one server? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the forum [0], the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something [1]. It may by processing a webpage written in PHP, processing a database querry or simply transfering a file.

[0] Using Moodle [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance forum]

[1] http://en.wikipedia.org/wiki/Concurrency_(computer_science)

===How do I benchmark a Moodle-site?===
You can ofcourse benchmark each component of the software stack, starting from the operating system upto the database https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark . But there is no easy formula to deduct the maximum number of concurrent users from those data.

There is a PHP-script [2] circulating amoung the Moodle-community which calculates a ballpark figure. Take the current version from 1. March 2007 posted here [3]. Please note running this script on a production server may have side-effects, you are strongly adviced to run it on a test-site.

[2] http://moodle.org/mod/forum/discuss.php?d=57028

[3] http://moodle.org/mod/forum/discuss.php?d=57028#p296907

===What are PHP-accelerators?===
For the definition see Wikipedia [4]. Read the Performance documentation [5] for possible software.

[4] http://en.wikipedia.org/wiki/PHP_accelerator

[5] https://docs.moodle.org/en/Performance#PHP_performance

===How do I cluster Moodle?===

http://moodle.org/mod/forum/discuss.php?d=57202

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What hardware is needed for N users?===
[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_hardware_is_needed_for_N_users.3F What hardware is needed for N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-09T14:58:00Z

Ratna: /* How many users will my installation support? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the forum [0], the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something [1]. It may by processing a webpage written in PHP, processing a database querry or simply transfering a file.

[0] Using Moodle [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance forum]

[1] http://en.wikipedia.org/wiki/Concurrency_(computer_science)

===How do I benchmark a Moodle-site?===
You can ofcourse benchmark each component of the software stack, starting from the operating system upto the database https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark . But there is no easy formula to deduct the maximum number of concurrent users from those data.

There is a PHP-script [2] circulating amoung the Moodle-community which calculates a ballpark figure. Take the current version from 1. March 2007 posted here [3]. Please note running this script on a production server may have side-effects, you are strongly adviced to run it on a test-site.

[2] http://moodle.org/mod/forum/discuss.php?d=57028

[3] http://moodle.org/mod/forum/discuss.php?d=57028#p296907

===What are PHP-accelerators?===
For the definition see Wikipedia [4]. Read the Performance documentation [5] for possible software.

[4] http://en.wikipedia.org/wiki/PHP_accelerator

[5] https://docs.moodle.org/en/Performance#PHP_performance

===How do I cluster Moodle?===

http://moodle.org/mod/forum/discuss.php?d=57202

===How do I replicate Moodle?===

===How do I setup multiple Moodle instances on one server?===
http://moodle.org/mod/forum/discuss.php?d=120757

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What hardware is needed for N users?===
[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_hardware_is_needed_for_N_users.3F What hardware is needed for N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-09T14:57:35Z

Ratna: /* How many users will my installation support? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the forum [0], the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something [1]. It may by processing a webpage written in PHP, processing a database querry or simply transfering a file.

[0] Using Moodle [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance forum]

[1] http://en.wikipedia.org/wiki/Concurrency_(computer_science)

===How do I benchmark a Moodle-site?===
You can ofcourse benchmark each component of the software stack, starting from the operating system upto the database https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark . But there is no easy formula to deduct the maximum number of concurrent users from those data.

There is a PHP-script [2] circulating amoung the Moodle-community which calculates a ballpark figure. Take the current version from 1. March 2007 posted here [3]. Please note running this script on a production server may have side-effects, you are strongly adviced to run it on a test-site.

[2] http://moodle.org/mod/forum/discuss.php?d=57028

[3] http://moodle.org/mod/forum/discuss.php?d=57028#p296907

===What are PHP-accelerators?===
For the definition see Wikipedia [4]. Read the Performance documentation [5] for possible software.

[4] http://en.wikipedia.org/wiki/PHP_accelerator

[5] https://docs.moodle.org/en/Performance#PHP_performance

===How do I cluster Moodle?===

http://moodle.org/mod/forum/discuss.php?d=57202

===How do I replicate Moodle?===

===How do I setup multiple Moodle instances on one server?===
http://moodle.org/mod/forum/discuss.php?d=120757

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What hardware is needed for N users?===
[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

See above [https://docs.moodle.org/en/Performance_FAQ#What_hardware_is_needed_for_N_users.3F N users?]

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-09T13:53:24Z

Ratna: /* What hosting provider do you recommend? */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the forum [0], the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something [1]. It may by processing a webpage written in PHP, processing a database querry or simply transfering a file.

[0] Using Moodle [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance forum]

[1] http://en.wikipedia.org/wiki/Concurrency_(computer_science)

===How do I benchmark a Moodle-site?===
You can ofcourse benchmark each component of the software stack, starting from the operating system upto the database https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark . But there is no easy formula to deduct the maximum number of concurrent users from those data.

There is a PHP-script [2] circulating amoung the Moodle-community which calculates a ballpark figure. Take the current version from 1. March 2007 posted here [3]. Please note running this script on a production server may have side-effects, you are strongly adviced to run it on a test-site.

[2] http://moodle.org/mod/forum/discuss.php?d=57028

[3] http://moodle.org/mod/forum/discuss.php?d=57028#p296907

===What are PHP-accelerators?===
For the definition see Wikipedia [4]. Read the Performance documentation [5] for possible software.

[4] http://en.wikipedia.org/wiki/PHP_accelerator

[5] https://docs.moodle.org/en/Performance#PHP_performance

===How do I cluster Moodle?===

http://moodle.org/mod/forum/discuss.php?d=57202

===How do I replicate Moodle?===

===How do I setup multiple Moodle instances on one server?===
http://moodle.org/mod/forum/discuss.php?d=120757

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What hardware is needed for N users?===
[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===
http://moodle.org/mod/forum/discuss.php?d=99405

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-09T13:52:10Z

Ratna:

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the forum [0], the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something [1]. It may by processing a webpage written in PHP, processing a database querry or simply transfering a file.

[0] Using Moodle [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance forum]

[1] http://en.wikipedia.org/wiki/Concurrency_(computer_science)

===How do I benchmark a Moodle-site?===
You can ofcourse benchmark each component of the software stack, starting from the operating system upto the database https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark . But there is no easy formula to deduct the maximum number of concurrent users from those data.

There is a PHP-script [2] circulating amoung the Moodle-community which calculates a ballpark figure. Take the current version from 1. March 2007 posted here [3]. Please note running this script on a production server may have side-effects, you are strongly adviced to run it on a test-site.

[2] http://moodle.org/mod/forum/discuss.php?d=57028

[3] http://moodle.org/mod/forum/discuss.php?d=57028#p296907

===What are PHP-accelerators?===
For the definition see Wikipedia [4]. Read the Performance documentation [5] for possible software.

[4] http://en.wikipedia.org/wiki/PHP_accelerator

[5] https://docs.moodle.org/en/Performance#PHP_performance

===How do I cluster Moodle?===

http://moodle.org/mod/forum/discuss.php?d=57202

===How do I replicate Moodle?===

===How do I setup multiple Moodle instances on one server?===
http://moodle.org/mod/forum/discuss.php?d=120757

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

http://moodle.org/mod/forum/discuss.php?d=102978
http://moodle.org/mod/forum/discuss.php?d=103040

===What hardware is needed for N users?===
[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]

Performance FAQ

2009-10-08T11:43:16Z

Ratna: /* Categories */

{{stub}}

===How do you define "concurrent users"?===
As has been repeatedly stressed in the forum [0], the load on the server depends primarily on the number of concurrent users, not on the total number of users neither the number of users logged-in at a given time. In this context, the concurrent users are those for whom the server actively doing something [1]. It may by processing a webpage written in PHP, processing a database querry or simply transfering a file.

[0] Using Moodle [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance forum]

[1] http://en.wikipedia.org/wiki/Concurrency_(computer_science)

===How do I benchmark a Moodle-site?===
You can ofcourse benchmark each component of the software stack, starting from the operating system upto the database https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark . But there is no easy formula to deduct the maximum number of concurrent users from those data.

There is a PHP-script [2] circulating amoung the Moodle-community which calculates a ballpark figure. Take the current version from 1. March 2007 posted here [3]. Please note running this script on a production server may have side-effects, you are strongly adviced to run it on a test-site.

[2] http://moodle.org/mod/forum/discuss.php?d=57028

[3] http://moodle.org/mod/forum/discuss.php?d=57028#p296907

===What are PHP-accelerators?===
For the definition see Wikipedia [4]. Read the Performance documentation [5] for possible software.

[4] http://en.wikipedia.org/wiki/PHP_accelerator

[5] https://docs.moodle.org/en/Performance#PHP_performance

===How do I cluster Moodle?===

===How do I replicate Moodle?===

===My site is very slow, what should I do?===

First find out "how slow". (The theme-trick here).

The next question is, whether the performance is normal or something malfunctions. There are many things which can malfunction:
* hardware
* crashed filesystems, specially network filesystems
* memory leaks or other crashes in the system
* bug in Moodle
* corrupted database

Or your performance could be "normal" under the given circumstances:
* Is it a root-server, dedicated server, virtual (shared) server
* How much RAM, processing power do you have?
* What is the software stack you use? (Unix or Windows, Apache or IIS, MySQL, PostgreSQL or SQL-Server, ...?)
* how many concurrent users slows the system down
* what modules/activities they use? Check [https://docs.moodle.org/en/Performance#Performance_of_different_Moodle_modules Performance of different Moodle modules]
* is your networt setup property? DNS, firewalls. Also check local firewalls and other local security tools?

[https://docs.moodle.org/en/Performance#Obtain_a_baseline_benchmark Obtain a baseline benchmark] and compare it with the published figures.

===What hardware is needed for N users?===
[http://moodle.org/mod/forum/discuss.php?d=111847 A moodle setup for 10K simultaneous users]

===How many users will my installation support?===

===Which operating system is the best?===

===What is the best webserver?===

===Should I go for 64 bit or is 32 bit OK?===

===What hosting provider do you recommend?===

[[Category:FAQ]] I [[Category: Administrator]] I [[Category:Performance]]