https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/YANGTOOLS-309 yangtools <p>DurationStatsTracker is calculating running average in the fast path, incurring at least 4 volatile reads, 2 double-precision multiplies, 1 double-precision division and two compare-and-swaps. Optionally this includes another 2 CASes and 2 volatile writes. Reading the stats afterwards is a breeze, though.</p> <p>This is obviously biased in the wrong direction, so it needs fixing.</p> <p>Operating System: All<br/> Platform: All</p> YANGTOOLS-309

DurationStatsTracker is highly inefficient

Bug Resolved Done Robert Varga Robert Varga Thu, 11 Sep 2014 14:01:23 +0000 Sun, 10 Apr 2022 18:35:19 +0000 Mon, 15 Sep 2014 09:48:26 +0000 0 2 <p>The easiest thing is to put a sync block around it then nothing needs to be volatile (or Atomic) and no CAS needed. The updates should really be done atomically anyway. Of course the get's would need to be sync'ed too. With sync block we'd hit just 1 write memory barrier instead 1 for each volatile. The lock overhead would be negligible as it would be uncontended, at least for commits which are single-threaded.</p> <p><a href="https://git.opendaylight.org/gerrit/11061" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/11061</a><br/> <a href="https://git.opendaylight.org/gerrit/11066" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/11066</a></p> Development External issue ID 1813 External issue URL ODL SR Target Milestone Rank 0|i026fj: