| Lucas_Werkmeister_WMDE added a comment. |
Do we really want to cache all constraint check results… or only those that we will actually show in the gadget: warning, violation and bad-parameters?
For reference: Berlin (Q64) currently has the following distribution of result statuses (P6320):
1344 "compliance" 196 "not-main-snak" 80 "todo" 73 "warning" 18 "deprecated" 1 "violation"
Of those 1712 results, the gadget only cares about 74. If we remove the rest, we massively reduce the size of the JSON we transmit and cache, which I suddenly find very tempting.
Of course, for this caching to still be correct, the API request has to explicitly indicate that it doesn’t care about the other results, and API requests without such an indication would not benefit from caching. Is that acceptable?
TASK DETAIL
EMAIL PREFERENCES
To: Lucas_Werkmeister_WMDE
Cc: Jonas, Aklapper, Lucas_Werkmeister_WMDE, Lahi, GoranSMilovanovic, QZanden, Agabi10, Wikidata-bugs, aude, Mbch331
Cc: Jonas, Aklapper, Lucas_Werkmeister_WMDE, Lahi, GoranSMilovanovic, QZanden, Agabi10, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
