<p>Thanks, <a href="https://github.com/tombeard" class="user-mention">@tombeard</a> - it works and appears safe. However, in my own (Centos) tests, CPU utilisation when workers are idle is noticeably higher than before.</p>
<p>Increasing the sleep duration helps - so if it is implemented this way then it should be exposed as a mod param with a sensible default.</p>
<p>Personally, it seems like a (mostly) unnecessary trade-off between CPU cycles and job-processing delay, for what appears to be a limited number of cases (FreeBSD only one reported to my knowledge). Mutex by default for the remainder seems to be both more efficient and 'real-time'.</p>
<p>If everyone else agrees the alternative approach is better all round, then I am happy to merge once the sleep duration has been made configurable. It would still be good to hear <a href="https://github.com/miconda" class="user-mention">@miconda</a>'s thoughts on making this a compile-time decision, though.</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/kamailio/kamailio/issues/822#issuecomment-290075638">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AF36Zcsegp3lwEHxlNawMcRnSMG4N7nJks5rqk-kgaJpZM4KWtZY">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AF36ZTqNhYGeF_PpslGLhzuFVH6HvxPWks5rqk-kgaJpZM4KWtZY.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/kamailio/kamailio/issues/822#issuecomment-290075638"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue 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/kamailio/kamailio","title":"kamailio/kamailio","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/kamailio/kamailio"}},"updates":{"snippets":[{"icon":"PERSON","message":"@charlesrchance in #822: Thanks, @tombeard - it works and appears safe. However, in my own (Centos) tests, CPU utilisation when workers are idle is noticeably higher than before.\r\n\r\nIncreasing the sleep duration helps - so if it is implemented this way then it should be exposed as a mod param with a sensible default.\r\n\r\nPersonally, it seems like a (mostly) unnecessary trade-off between CPU cycles and job-processing delay, for what appears to be a limited number of cases (FreeBSD only one reported to my knowledge). Mutex by default for the remainder seems to be both more efficient and 'real-time'.\r\n\r\nIf everyone else agrees the alternative approach is better all round, then I am happy to merge once the sleep duration has been made configurable. It would still be good to hear @miconda's thoughts on making this a compile-time decision, though."}],"action":{"name":"View Issue","url":"https://github.com/kamailio/kamailio/issues/822#issuecomment-290075638"}}}</script>