Re: lockstat from pathological builds Re: high sys time, very very slow builds on new 24-core system

2011-04-01 Thread Thor Lancelot Simon
On Thu, Mar 31, 2011 at 04:32:12PM -0400, Thor Lancelot Simon wrote: On Thu, Mar 24, 2011 at 12:04:02PM +, Andrew Doran wrote: Try lockstat as suggested to see if something pathological is going on. In addition to showing lock contention problems it can often highlight a code path

Re: lockstat from pathological builds Re: high sys time, very very slow builds on new 24-core system

2011-04-01 Thread Andrew Doran
On Fri, Apr 01, 2011 at 01:05:02PM -0400, Thor Lancelot Simon wrote: On Thu, Mar 31, 2011 at 04:32:12PM -0400, Thor Lancelot Simon wrote: On Thu, Mar 24, 2011 at 12:04:02PM +, Andrew Doran wrote: Try lockstat as suggested to see if something pathological is going on. In

Re: lockstat from pathological builds Re: high sys time, very very slow builds on new 24-core system

2011-04-01 Thread Kevin Bowling
On 4/1/2011 1:47 PM, Andrew Doran wrote: On Fri, Apr 01, 2011 at 01:05:02PM -0400, Thor Lancelot Simon wrote: On Thu, Mar 31, 2011 at 04:32:12PM -0400, Thor Lancelot Simon wrote: On Thu, Mar 24, 2011 at 12:04:02PM +, Andrew Doran wrote: Try lockstat as suggested to see if something

Re: high sys time, very very slow builds on new 24-core system

2011-03-31 Thread Thor Lancelot Simon
On Wed, Mar 23, 2011 at 05:24:12PM -0400, Thor Lancelot Simon wrote: All cores spend well over 50% time in 'sys', even when all or almost all are running cc1 processes. The kernel is amd64 -current GENERIC from about 1 week ago -- no DIAGNOSTIC, DEBUG, KMEMSTATS, LOCKDEBUG, etc. I am

Re: high sys time, very very slow builds on new 24-core system

2011-03-31 Thread Julio Merino
On Thu, Mar 31, 2011 at 8:53 PM, Thor Lancelot Simon t...@panix.com wrote: [...]           I wonder if some tool has reverted to using /var/tmp for its           intermediate files, or similar.  Don't see an obvious           culprit for that, however. gcc uses /var/tmp by default unless you

Re: high sys time, very very slow builds on new 24-core system

2011-03-25 Thread Mindaugas Rasiukevicius
Andrew Doran a...@netbsd.org wrote: We have some algorhythms in the scheduler and mutual exclusion code that aren't designed for large numbers of cores, but I think they should be OK with 24 CPUs. ... I have committed mutex_oncpu patch, so it is O(1) in -current. ... (While I'm rambling

Re: high sys time, very very slow builds on new 24-core system

2011-03-24 Thread Christoph Egger
On 03/23/11 22:24, Thor Lancelot Simon wrote: I have a new machine with 24 2Ghz Opteron cores. It has 32GB of RAM. Building with sources on a fast SSD (preloaded into the page cache before the build using tar /dev/null) and obj, dest, and rel dirs on tmpfs, system builds are extraordinarily

Re: high sys time, very very slow builds on new 24-core system

2011-03-24 Thread Andrew Doran
On Wed, Mar 23, 2011 at 05:24:12PM -0400, Thor Lancelot Simon wrote: I have a new machine with 24 2Ghz Opteron cores. It has 32GB of RAM. Building with sources on a fast SSD (preloaded into the page cache before the build using tar /dev/null) and obj, dest, and rel dirs on tmpfs, system

Re: high sys time, very very slow builds on new 24-core system

2011-03-24 Thread Thor Lancelot Simon
On Thu, Mar 24, 2011 at 04:05:07PM +, Eduardo Horvath wrote: On Thu, 24 Mar 2011, Andrew Doran wrote: I have a suspicion that SSD could cause issues for us because the buffer cache and other parts of the I/O system are not designed with near instantaneous request-response in mind, but

Re: high sys time, very very slow builds on new 24-core system

2011-03-23 Thread Eduardo Horvath
On Wed, 23 Mar 2011, Thor Lancelot Simon wrote: I have a new machine with 24 2Ghz Opteron cores. It has 32GB of RAM. Building with sources on a fast SSD (preloaded into the page cache before the build using tar /dev/null) and obj, dest, and rel dirs on tmpfs, system builds are

Re: high sys time, very very slow builds on new 24-core system

2011-03-23 Thread Jukka Ruohonen
On Wed, Mar 23, 2011 at 05:24:12PM -0400, Thor Lancelot Simon wrote: All cores spend well over 50% time in 'sys', even when all or almost all are running cc1 processes. The kernel is amd64 -current GENERIC from about 1 week ago -- no DIAGNOSTIC, DEBUG, KMEMSTATS, LOCKDEBUG, etc. Does