In message <19980217033329.49630@is.co.za>, Oskar Pearson writes:
> > Check to see if it's the main thread burning CPU, or one of the child
> > threads...
>
> Each of the child threads..
'ps uaxr' is a handy thing here. 'top' gives a very distorted view of
life.
>
> squid@newt:/usr/local/squid/bin > time ./squid
> real 3m10.029s
> user 0m1.320s
> sys 0m3.080s
> huh?
time ./squid -N ?
> hmm... I should have used 'strace -f':
>
> hmm. That's just great... when I strace -f it doesn't chew CPU!
Laugh. Try leaving it for a while. I've noticed that the children burn
a bit of CPU on startup, but they do settle down. I suspect it's an
issue with the threads library again.
Note that you can't strace a thread. And attempting to do so will stop
it, so you need to 'kill -CONT <tid>' to keep things happy.
# ps uaxr
USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND
root 4355 0.0 0.0 956 392 p3 R 09:36 0:00 ps uaxr
squid 4247 69.6 41.7 217404 215196 ? R 09:14 14:59 /opt/s2/bin/squid -N -C
squid 4260 0.4 41.7 217404 215196 ? D 09:14 0:05 /opt/s2/bin/squid -N -C
squid 4261 0.3 41.7 217404 215196 ? D 09:14 0:04 /opt/s2/bin/squid -N -C
Thats a 1.2b11 + patches, so it's not directly comparable. Is b15
working for you other than burning CPU time? I might give it a shot
again.
Michael.
Received on Tue Jul 29 2003 - 13:15:46 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:11:42 MST