Good day,
I have a problem here,my moodle server become very very slow (almost hang!) when the concurrent user is around 90. Is there any way to tune and optimize the performance? like mysql? httpd?
my server spec : -
Pentium Xeon, 4GB Ram, 70Gb Hardisk ;
Fedora Core 5, moodle version 1.5.3;
Thanks in advice. Cheers !
This is about asking what color should I paint my house. There are so many variables involved here in the .conf files that the question is virtually impossible to answer with the information given.
I would "google" optimize mysql and apache and at least get an idea of numbers that need to fill in the blanks. Also, by default, mysql has caching turned off, turning it on can do wonders (works best on sites with a lot of static data). Reductions on disk reads can reach 75% or more (caching only works on unchanged data fields).
What would be helpful would be some more data on what is going on with the server. Bottleneck fixes are easier when you know what they are. Look at installing something like "Munin". This can pinpoint the bottleneck and knowing what to fix is a big time saver.
If this is a production environment, it would probably be to your benefit to use a third party to bring that server up to speed without down time (bad setting's can be disastrous). If you need recommendations for this type of service I can send you links to a couple I have used on my servers in the past.
<With the Apache+PHP memory model it is perfectly possible
>
Are you referring to segmentation? Sorry i am not familiar with this term in this context. Anyway, with servers even in shared environments, a single P4 2.4 Ghz w/2G of memory, 50 to 90 concurrent users is do-able. As Moodle seems to be most intensive on the mysql db, is why I was wondering what was going on with the mysql cache file. (a program called "mytop" works rather nicely for this).
It does occur to me that if the swap is perhaps to small, (if the system was even swapping to disk) it could be an issue.
For diagnosis I prefer a graphing program like Munin that tracks virtually every aspect of the boxes activity and plots it in an easy to see format. Trends are just easier to follow IMO.
Briefly, to prevent Apache bloat, you can try lowering MaxRequestsPerChild and perhaps the PHP memory limit as well (about 16M).
Past discussion on memory consumption tuning.
Perhaps the Performance section in the wiki could be expanded to more than one page's worth seeing as there's so much info located in past forum threads.
