On Thu, May 06, 2004, P.D. Seniura wrote: > > > > It seems this bug happens when the HZ value goes below 16 > > > (either by compiling 'options HZ=' in kernel or setting > > > sysctl 'kern.hz=' in /boot/loader.conf). The computed > > > 'ticks' value becomes too large for 2-byte int producing > > > crazy overflowed numbers elsewhere. > > > > 16 is pretty low.. > > Then again it would be nice if it warned you or something similar when you > > tried it :) > > Heh, I got HZ set to 20 while it does > buildworld (~9 hours) and portupgrade overnight. > The idea is "less slicing and more doing". ;) Umm...yeah, don't do that. For one, 1/(100 Hz) = 10000 us = 4.5 million cycles on your processor, which is an eternity in computer time. For two, HZ doesn't affect the maximum timeslice processes get. The scheduling quantum is fixed at 100 ms in the 4BSD scheduler, and it varies between 10 ms and 143 ms in ULE.Received on Thu May 06 2004 - 19:08:59 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:53 UTC