lock contention - what can we do about it?

[Milian Wolff]

Alexander Shaduri, 06.03.2011:
> Hello,
> 
> On Sat, 5 Mar 2011 20:17:35 +0100
> 
> Milian Wolff wrote:
> > 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).
> 
> I may be totally wrong here, but could you not use tmpfs or something
> like that for the files in question to rule out I/O bottleneck?
> 
> Cheers,
> Alexander

good idea, but I'm not sure how this is done, esp. with the system includes... 
can I remount /usr/include on a tmpfs?

bye
-- 
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/20110306/a5d44c4e/attachment.sig>