> Again, we're not sure. Of course, reducing the load (both in terms of edits on Wikidata and of reads on WDQS) will help. But not using those services makes them useless.
What about making the lag part of the service. I mean, you could
reload WDQS periodically, for instance daily, and drop the updater
altogether. Who needs to see the updates live in WDQS as soon as edits
are done in wikidata?
I think Wikidata editors are the ones that really need up-to-date query results as a form of feedback (e.g., to check if imports are okay or QuickStatements batches are done right).
It might make sense to explore having two WDQS instances:
1. Public instance that is only updated daily or even weekly
2. Community instance that is up-to-date and where you need to log-in with your Wikimedia user account and therefore we can control access to via whitelisting or blacklisting