MoodleDoc about Apache recommended settings up-to-date ?

MoodleDoc about Apache recommended settings up-to-date ?

by Philip Siwinski -
Number of replies: 4

Hi,

I'm experiencing performance issues with Moodle 2.1.2.

In my investigation, could you confirm me that the recommended Apache settings from the MoodleDocs still work well with Moodle 2 ?

Here they are:

Timeout 200
KeepAlive On
MaxKeepAliveRequests 200
KeepAliveTimeout 3
MinSpareServers 5
MaxSpareServers 15
StartServers 5
MaxClients 20
MaxRequestsPerChild 2000
HostnameLookups Off


Thank you.
Average of ratings: -
In reply to Philip Siwinski

Re: MoodleDoc about Apache recommended settings up-to-date ?

by Emma Richardson -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers

I was having considerable performance issues - I have tweaked my settings as follows and it has helped a lot:

KeepAliveTimeout 2

MinSpareServers 1

MaxSpareServers 2

StartServers 2

MaxClients 25

MaxRequestsPerChild 200

 

This seems to have stopped my server from crashing and while I still see some slow downs when a whole class is taking a test, everyone has always beee able to log on now and site overall is much faster.  I am running on a virtual Debian Squeeze with 4GB ram.

In reply to Emma Richardson

Re: MoodleDoc about Apache recommended settings up-to-date ?

by Philip Siwinski -

Thank you Emma, I'll give a try soon.

How many concurrent users do you deal with, more or less ?

In reply to Philip Siwinski

Re: MoodleDoc about Apache recommended settings up-to-date ?

by Emma Richardson -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers

Pretty small site for the most part.  Normally about 10 concurrent users but been running into issues when a class of 28 logs in to take a test.

In reply to Philip Siwinski

Re: MoodleDoc about Apache recommended settings up-to-date ?

by Philip Siwinski -

I have finally moved Moodle to a fresh installed server with more resources without changing any Apache setting. It works well with 50+ concurrent users now.

Thanks for your help.