lock contention - what can we do about it?

Milian Wolff mail at milianw.de
Sat Mar 5 19:17:35 UTC 2011


David Nolden, 05.03.2011:
> If the CPU time is below 100%, then that's for sure not due to lock
> contention, but simply due to I/O. Either repeat the test with the
> disk-cache better filled, or increase the number of threads.

If that would be the case, wouldn't iotop show lots of disk access? And top's 
%wa would be high, but it's rarely more than 2% for me (wa is iowait time).

-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110305/35bfe256/attachment-0001.sig>


More information about the KDevelop-devel mailing list