Revision as of 06:48, 13 March 2020 edit Artoria2e5 (talk \| contribs) Extended confirmed users, IP block exemptions 38,988 edits →Unix-style load calculation ← Previous edit		Revision as of 11:05, 7 May 2020 edit undo John of Reading (talk \| contribs) Autopatrolled, Extended confirmed users, Pending changes reviewers 787,577 edits m →Reckoning CPU load: Typo fixing, replaced: refereshes → refreshes Tag: AWB Next edit →
Line 73: </source> The "sampled" calculation of load averages is a somewhat common behavior; FreeBSD, too, only ~~refereshes~~refreshes the value every five seconds. The interval is usually taken to not be exact so that they do not collect processes that are scheduled to fire at a certain moment.<ref>{{cite web \|title=How is load average calculated on FreeBSD? \|url=https://unix.stackexchange.com/a/342778 \|website=Unix & Linux Stack Exchange}}</ref> A post on the Linux mailing list considers its {{tt\|+1}} tick insufficient to avoid Moire artifacts from such collection, and suggests an interval of 4.61 seconds instead.<ref>{{cite web \|last1=Ripke \|first1=Klaus \|title=Linux-Kernel Archive: LOAD_FREQ (4*HZ+61) avoids loadavg Moire \|url=http://lkml.iu.edu/hypermail/linux/kernel/1111.1/02446.html \|website=lkml.iu.edu \|date=2011}} [http://ripke.com/loadavg/moire graph & patch]</ref> This change is common among [[Android system]] kernels, although the exact expression used assumes an HZ of 100.<ref>{{cite web \|title=Patch kernel with the 4.61s load thing · Issue #2109 · AOSC-Dev/aosc-os-abbs \|url=https://github.com/AOSC-Dev/aosc-os-abbs/issues/2109 \|website=GitHub \|language=en}}</ref>

Load (computing): Difference between revisions