On Sun, Sep 26, 2004 at 10:12:18PM +0930, Daniel O'Connor wrote: > On Sun, 26 Sep 2004 21:16, Ryan Freeman wrote: > > > I suspect that sysctl involves doing lots of locking and will do weird > > > things.. > > > Does it happen if you run a CPU using userland proc inseadt? > > > > The problem is, it isn't just that sysctl command that does it. I find that > > even running gkrellm makes the ticking worse. if i close gkrellm, it > > I'd say gkrellm probably pokes at various sysctl's to gather stats so it may > be a related problem. > > > reduces the ticks/sound stretches. that sysctl was just an easy way to make > > the problem _really_ stand out it seems. iirc when i was using 5.2.1 i > > found that just disabling the proc chart in gkrellm seemed to help a lot. > > haven't bothered to try it now. > > Does a purely CPU bound process cause the problem? > ie try something like.. > dd if=/dev/zero | md5 > well i gave that command a shot (i closed gkrellm first to reduce any clicking that may happen from it running) then started an mp3 with mpg123 alongside running that command. didn't skip a beat, so i guess its all related to sysctl... - ryanReceived on Sun Sep 26 2004 - 10:54:08 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:13 UTC