CURRENT inside MS Virtual Server 2005
Yar Tikhiy
yar at comp.chem.msu.su
Thu Mar 3 08:19:25 GMT 2005
On Tue, Mar 01, 2005 at 05:01:27PM +0100, Dag-Erling Sm?rgrav wrote:
> Yar Tikhiy <yar at comp.chem.msu.su> writes:
> > 4.x and 5.x run smoothly in this virtual environment, but CURRENT
> > spends 20-30% of CPU time in the "swi4: clock sio" thread.
> > Moreover, CPU idle time data look really weird. Neither tweaking
> > kern.timecounter.hardware nor disabling ACPI seems to affect that.
>
> try adding 'kern.hz=100' to /boot/loader.conf.
This fixed idle time accounting, but the clock thread still is
eating a lot of CPU time. It's not a big deal since its CPU time
drops as soon as a real task starts, but the whole picture looks a
bit weird. Do you have an idea why the clock thread behaves this way?
Thanks!
%%%
yar at current:~$sysctl kern.clockrate
kern.clockrate: { hz = 100, tick = 10000, profhz = 1024, stathz = 128 }
yar at current:~$top -S
...
CPU states: 0.0% user, 0.0% nice, 2.7% system, 18.9% interrupt, 78.4% idle
Mem: 6012K Active, 4860K Inact, 10M Wired, 7920K Buf, 100M Free
Swap: 231M Total, 231M Free
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
11 root 171 52 0K 8K RUN 6:13 74.17% 74.17% idle
27 root -32 -151 0K 8K *Giant 0:08 17.97% 17.97% swi4: clock sio
...
yar at current:~$gzip < /dev/zero > /dev/null &
yar at current:~$top -S
...
CPU states: 69.1% user, 0.0% nice, 27.2% system, 3.7% interrupt, 0.0% idle
Mem: 6668K Active, 5800K Inact, 11M Wired, 8816K Buf, 98M Free
Swap: 231M Total, 231M Free
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
473 yar 132 0 1532K 1016K RUN 7:00 92.97% 92.97% gzip
27 root -32 -151 0K 8K WAIT 0:18 2.98% 2.98% swi4: clock sio
...
%%%
--
Yar
More information about the freebsd-current
mailing list