<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 27 October 2014 17:27, Ben Shelton <span dir="ltr"><<a href="mailto:ben.shelton@ni.com" target="_blank">ben.shelton@ni.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2ac" class="a3s" style="overflow:hidden">In the commit 'prserv: Ensure data is committed', the PR server moved to<br>
only committing transactions to the database when the PR server is<br>
stopped. This improves performance, but it means that if the machine<br>
running the PR server loses power unexpectedly or if the PR server<br>
process gets SIGKILL, the uncommitted package revision data is lost.<br>
<br>
To fix this issue, <span class="il">sync</span> the database periodically, once per 30 seconds<br>
by default, if it has been marked as dirty. To be safe, continue to<br>
<span class="il">sync</span> the database at exit regardless of its status.</div></blockquote></div><br>This appears to be causing random problems for me where bitbake will timeout attempting to access the PR database, my hunch is that it's blocking on disk I/O. Are there any tricks we can do with sqlite to reduce the overhead of committing? (assuming that sqlite isn't causing a full filesystem sync).</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>