Development guideline for database optimization
User:Leucosticte declared this a "development guideline", so I switched this page to Draft. Krenair also noticed that it specifically named Asher, which was dated information as well.
- This is a bit poor. Nothing here is wrong in a quick read, but the content is very light. I will try to add some generally applied techniques and recommendations, specially for testing results. --Jynus (talk) 14:19, 24 November 2015 (UTC)
Flushing stale reads
@Aaron Schulz: the page says, Always be aware of stale reads caused by REPEATABLE-READ isolation, flushing transactions as needed. A pointer on how to do that would be nice. There is an
IDatabase::flushSnapshot method, but it seems like it would be highly unsafe in almost all circumstances as it throws an error if there is a pending precommit callback and usually there is no way to guarantee that some other part of the code (possibly behind a hook) didn't add one. --Tgr (WMF) (talk) 23:04, 9 January 2018 (UTC)