| Lucas_Werkmeister_WMDE added a comment. |
what about invalidating constraint check results when a constraint statement is edited?
This Grafana chart shows how the rate of constraintsTableUpdate jobs dropped with the deployment of T182110: Only update constraints table when constraint statements were edited. At a glance, it seems like roughly one tenth of all property changes affect the constraints (the avg in the chart drops by about one order of magnitude). So it might be worth trying to only invalidate cached check results when the property statements change, but for a first version we can probably do without it, and only track the full property revision ID.
TASK DETAIL
EMAIL PREFERENCES
To: Lucas_Werkmeister_WMDE
Cc: Jonas, Aklapper, Lucas_Werkmeister_WMDE, Lahi, Gq86, GoranSMilovanovic, QZanden, Agabi10, Wikidata-bugs, aude, Mbch331
Cc: Jonas, Aklapper, Lucas_Werkmeister_WMDE, Lahi, Gq86, GoranSMilovanovic, QZanden, Agabi10, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
