https://bugzilla.wikimedia.org/show_bug.cgi?id=32679
--- Comment #3 from Reedy <s...@reedyboy.net> 2011-11-28 12:48:40 UTC --- Indeed. From a european point of view (myself, Mark and Ariel), it was getting late, and for the Americans it was a holiday weekend. Hence, disabling the extension outright was the simplest fix until a more appropriate time to evaluate and sort the extension, and then we knew it wouldn't do any more harm till it was completely assessed. On the optimisation note, Domas gave Arthur and Ryan (Kaldari) reasonable instructions on how to fix it up (hopefully in the near term) so it would work a lot better under load. It has been known for a long time that the underlying database is poorly indexed and the alike. It might just be mainly one path through the code, but Mark did see a lot of slow queries that seem to have originated from the "maximumsMax" code. Looking at the surrounding code all the other code paths seem to do similarly bad queries, so I'm not holding out much hope >From the top of my head, we don't have a "nice" way to mark special pages as disabled, so it's likely going to need a hack on that special page itself. The rest of the extension may be fine to re-enable (the other special pages) -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
