I love you. And I mean it from the bottom of my heart. On October, 22nd, I upgraded to moodle 1.8.3+. Take a look at the number of queries before and after...
thanks,
Maik
What was the version and date of the code that you were upgrading from? That graph does say it all. Or as Napoleon Dynamite would say, "Sweet!"
Nice graph, thanks!
Oh - I've got more of this. It is the munin package of debian. So If you are interested in RAM-usage...
I spend a long time to optimize the MySQL-settings to get this cache hitrate.
I spend a long time to optimize the MySQL-settings to get this cache hitrate.
Maik
Well since you are offering, what is your best advice for optimizing the MySQL settings?
It heavily depends on your installation and your users. A good point to start is the following link (tuning_primer.sh):
http://day32.com/MySQL/
Another hint is to turn any engine og MySQL off, you won't need, especially InnoDB to save memory.
We use lighttpd instead of apache - this saves much memory - but no one seems to have tested this on high load environments. I've got 30% more performance since using lighttpd/fastCGI.
http://day32.com/MySQL/
Another hint is to turn any engine og MySQL off, you won't need, especially InnoDB to save memory.
We use lighttpd instead of apache - this saves much memory - but no one seems to have tested this on high load environments. I've got 30% more performance since using lighttpd/fastCGI.
Maik
Hi Maik,
I am wondering what your max concurrent users are when using lighttpd/fastcgi. Perhaps a good option for us.
Whan you speak of performance what do you mean exactly, faster response time on pages, or less load on the server?
I am wondering what your max concurrent users are when using lighttpd/fastcgi. Perhaps a good option for us.
Whan you speak of performance what do you mean exactly, faster response time on pages, or less load on the server?