|
From: Eyal L. <ey...@ey...> - 2003-03-15 07:10:26
|
I am using valgrind to test a heavily multithreaded client/server system and I suspect that the 98% idle CPU during much of the run is an indication of room for improvement. I started looking at the general logic of the scheduler and could not understand those unusual nanosleeps (various ms durations). I changed them all to 1ms (1 * 1000 * 1000) and my tests now complete in half the time (not bad for what was an 18 hours run last time). Since the machine is fully dedicated to this run, I am happy to have the CPU busy when no thread is ready. Probably a simple yield at that point is all one needs to give other processes a chance. So far I am unable to read the list archive so I will refrain from asking questions that may be FAQs. Any help with accessing the list archive will be appreciated - I simply go to https://lists.sourceforge.net/lists/listinfo/valgrind-developers and follow the link to the "collection of prior postings" just to be greeted with ERROR Forum is restricted to members of this group -- Eyal Lebedinsky (ey...@ey...) <http://samba.org/eyal/> |