| Betacommand added a comment. |
In T159618#3080947, @Legoktm wrote:In T159618#3079361, @Esc3300 wrote:I think it might be worth attempting to determine the factors that lead to the rapid raise.
- The edit rate didn't seem that high and we could easily have several bots that resulted in the same rate.
I disagree. According to https://wikipulse.herokuapp.com/, the edit rate on Wikidata right now is anywhere from 150-220 epm. Adding an extra 600 epm on top of that is what caused the problem.
The edit rate may have been the issue, but we should still utilize the tools we have (maxlag) to notify bots that the server is under high load. If we throw a check in maxlag value calculation checking for the number of JobQueue entries and then raising the maxlag to indicate it, it would prevent bots from causing this issue again. Regardless of whether its one bot or several causing the spike, the existing maxlag checks could be used to notify all bots to back off.
Cc: Esc3300, Lydia_Pintscher, Emijrp, Betacommand, BethNaught, TerraCodes, Jay8g, Joe, aaron, Legoktm, Aklapper, Th3d3v1ls, Hfbn0, Zppix, D3r1ck01, Izno, Wikidata-bugs, aude, faidon, Mbch331, fgiunchedi
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
