On Monday 23 April 2007 00:52, Paul wrote: > >Uh you had the right idea but forgot to paste the relevant bits ;-) > > > >top *is* the tool for working out what processes are using your CPU. > >Although your high load average suggests that your system is just > >heavily loaded and it is expected that it will be using 100% CPU. > > > >Kris > > Dear Kris, > > Thanks for your e-mail. > > The odd thing is that I just switched from an old 4.12 box with dual > xeon (only 2 processors) with 4 gb of ram to the 6.2 with the extra > ram and dual core dual zeons (technically twice the cpus:) and 4* the > ram.... > > This one is dying and the other older "so called slower" system works > much better with as close to the same configuration as I can make it. > > I have to assume something is wrong here but I will keep digging as > this is not even workable. > > The system cpu is still high if I get rid of the memory drive and > have it save on the disks. It takes a lifetime to build a kernel now... > > Any way I can view what is made up of the 50-70% system cpu to be > able to pinpoint the bottleneck? > > I have tried to trim down the ipfw rules to see if this was the > culprit but this does not seem to be making a difference so far.
"vmstat -i" could help to rule out interrupt storms. "top -S" will show in-kernel threads as will "systat". Maybe these help. -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News
pgpreN8AUXrTf.pgp
Description: PGP signature
