jcrespo added a comment.

@aude If you are increasing the priority based on my comment, don't. Regular 
databases can handle the extra load (for now), the main issue is in research 
databases or labs, where they contain all dbs, or when there is maintenance and 
we are in a degraded state. This currently is not a user-notice, but it is 
important enough to discuss a way to solve it.

So the issue is that extra writes are not a problem for our masters -they are 
done concurrently-, but when we try to scale out, most of the writes are 
serialized on the logs, and there has been many times when there are lag 
problems that the current queries being executer are these. I do not thing the 
queries are slow- but I may be wrong, do not have statistics. You are right: 
let's get numbers first: how many are executed and how much time it takes (and 
for myself, I need to fully understand the model) before rushing into solutions 
(my suggestion was a bit premature).


TASK DETAIL
  https://phabricator.wikimedia.org/T107319

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: jcrespo
Cc: jcrespo, Aklapper, aude, Wikidata-bugs, Malyacko



_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to