It's been 11 hours since the Twitter news went up to say we are "Experiencing problems"
That's a long time to go with no news. Does anyone know?
If Moodle.org is going to use this as a communication channel, how about a Twitter feed on the front page of Moodle.org as well . . .
-Derek.
Is anyone there?
This is the third time Moodle.org has gone down or slow or stopped notifications for a long period of time and no news has seeped out. Is there a place we need to go to to keep up with things?
I assumed it was Twitter, but https://twitter.com/search?q=moodlesites isn't it.
-Derek
Just as too many cooks spoil the broth, too many posts spoil the message
https://moodle.org/mod/forum/discuss.php?d=255580
https://moodle.org/mod/forum/discuss.php?d=255664
But yes, where there is smoke there is fire!
Sorry I've been on holiday for a few days, and just heard there was a temporary problem which has now been resolved.
"Is there a place we need to go to to keep up with things?"
I would say https://twitter.com/moodlesites and https://tracker.moodle.org/browse/MDLSITE also I like to check http://isup.me/moodle.org to see whether it's just me having the problem.
Hi folks,
Just to follow up on this, apologies for the lack of comms, I've been primarily focused on finding the root cause of the problem and resolving it.
The load time issue was related to database load, which needed some additional key tuning, as well as a couple of indexes added to a custom table we're using to keep track of stats.
The addition of the indexes alone reduced the query time for a specific stats lookup from ~ 5 minutes 40 seconds, down to 0.77 seconds (cached).
The same query after tuning adjustments (non-cached) now takes 2.7 seconds, cached returns results immediately (mysql says 0.00 sec)
Server load (although not exactly meaningful without context) dropped from ~ 87 to now being stable between 0.5 and 2.
Apologies for the the inconvenience and thanks for your patience.
Matt
Hi Matthew,
That sure was a superb job!