<p>To your other question we're still trying to come up with numbers, the system has many things going on and showing something 100% attributable to this is hard - I'm trying to see if we can get a more exact A/B test.</p>
<p>madvise() doesn't help ensure there's less dirty data in the system, which is different from what you are describing. If the write-queue becomes too long, then anything else that needs to write now has to wait... which doesn't work well with a database load. Now mysql sync's and has to wait for a half-gig of data to be flushed. That's a problem.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/rpm-software-management/rpm/pull/187#issuecomment-292278640">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb800I-lJD8IxA1fJDgqa1qiuww89Zvks5rtTZ0gaJpZM4MyLOi">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb800y7cJcyXd8ckWKv1H-cZ0Gm-S4Vks5rtTZ0gaJpZM4MyLOi.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/rpm-software-management/rpm/pull/187#issuecomment-292278640"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/rpm-software-management/rpm","title":"rpm-software-management/rpm","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/rpm-software-management/rpm"}},"updates":{"snippets":[{"icon":"PERSON","message":"@jaymzh in #187: To your other question we're still trying to come up with numbers, the system has many things going on and showing something 100% attributable to this is hard - I'm trying to see if we can get a more exact A/B test.\r\n\r\nmadvise() doesn't help ensure there's less dirty data in the system, which is different from what you are describing. If the write-queue becomes too long, then anything else that needs to write now has to wait... which doesn't work well with a database load. Now mysql sync's and has to wait for a half-gig of data to be flushed. That's a problem."}],"action":{"name":"View Pull Request","url":"https://github.com/rpm-software-management/rpm/pull/187#issuecomment-292278640"}}}</script>