Date: Mon, 25 Feb 2008 19:54:08 +0100 From: Daniel Gerzo <danger@FreeBSD.org> To: Jeff Roberson <jroberson@chesapeake.net> Cc: Daniel Gerzo <danger@FreeBSD.org>, freebsd-current@FreeBSD.org, Ivan Voras <ivoras@FreeBSD.org> Subject: Re[3]: cpu usage in 7.0 Message-ID: <1855464401.20080225195408@rulez.sk> In-Reply-To: <20080224223903.Q920@desktop> References: <845250.18624.qm@web63909.mail.re1.yahoo.com> <47BF5702.3020204@FreeBSD.org> <47BF8EB7.9090007@barafranca.com> <47BFB70F.5080402@FreeBSD.org> <fpslt8$fjj$1@ger.gmane.org> <20080224124342.E920@desktop> <1172441424.20080225092945@rulez.sk> <20080224223903.Q920@desktop>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Jeff, Monday, February 25, 2008, 9:41:37 AM, you wrote: >> I have a box running mysqld, which sometimes exeeds 130%, what about >> this? ;) >> >> Also the mysqld is alsmost all the time in the "ucond" state, what >> does it mean? I've been told that it is probably waiting for I/O, but >> then, I have another box which is currently completely idle, but >> running mysql shows that it is "ucond" as well. > You should switch top to display threads. 'H' is the key to do it. > Otherwise you only get the wait channel for one of the threads. Others > may be busy doing things. This is correct. > 'ucond' means the thread is waiting on a userland condition variable. > This is a type of synchronization point in userland accessed via the > pthread_cond_*(3) api. It may indicate a thread that is waiting for work > but other threads may be busy. OK, thank you for the explanation. > Do you only have one CPU? If you're seeing 130% on a single cpu system we > may need to take some steps to improve the reporting. No, actually this is AMD Athlon64 X2, so dualcore, so may I assume 130% is OK for dualcore? -- Best regards, Daniel mailto:danger@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1855464401.20080225195408>