| MisterSynergy added a comment. |
How much are we sure that this problem was predominantly caused by the recently “high” edit rate (or undesired number of parallel bot runs) at Wikidata? At Wikidata we are trying to get edit rates down, but I am uncomfortable with the notion that Wikidata operates already at the edge of what’s technically possible. Recent activity might have been pretty high, but not that much that I would have expected problems of that impact.
I would like to point to the dispatch graphs [1] in Grafana as well. If you look closely, there seems to be a very clear singularity in many of the graphs on 2017-06-28, between 21:15 and 21:30 (Grafana time, no idea whether this is UTC). What happend at this time? If there was a software or hardware failure, it probably would have been noticed by today, but this does not seem to be the case according to the Grafana charts. I thus speculate that some very expensive new software was deployed at this singularity, or an update which is badly inefficient compared to the previous condition. The history of T151681 (and maybe other tasks) indicates that there was in fact activity in connection with the dispatcher around that time.
[1] https://grafana.wikimedia.org/dashboard/db/wikidata-dispatch?refresh=1m&orgId=1
Cc: MisterSynergy, Liuxinyu970226, daniel, Esc3300, XXN, Ladsgroup, Lydia_Pintscher, hoo, Bugreporter, Sjoerddebruin, Magnus, Emijrp, Mr.Ibrahem, Wikidata, Aklapper, PokestarFan, GoranSMilovanovic, QZanden, Vali.matei, Volker_E, Izno, Wikidata-bugs, aude, GWicke, Mbch331, Jay8g
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
