Re: moz.build processing time

2016-11-28 Thread Gregory Szorc
On Sat, Nov 26, 2016 at 9:31 AM, Ehsan Akhgari wrote: > On 2016-11-24 7:04 PM, Nathan Froyd wrote: > > On Wed, Nov 23, 2016 at 4:31 PM, Mike Hommey wrote: > >> I know OSX can be bad with I/O, but that seems unusually bad. IIRC gps > >> found that there's a relatively low limit to the number of f

Re: moz.build processing time

2016-11-26 Thread Ehsan Akhgari
On 2016-11-24 7:04 PM, Nathan Froyd wrote: > On Wed, Nov 23, 2016 at 4:31 PM, Mike Hommey wrote: >> I know OSX can be bad with I/O, but that seems unusually bad. IIRC gps >> found that there's a relatively low limit to the number of files or >> inodes that can be in cache, and a working tree of m-

Re: moz.build processing time

2016-11-24 Thread J. Ryan Stinnett
On Thu, Nov 24, 2016 at 6:23 PM, Mike Hommey wrote: > Sounds like something we could query from `mach doctor`. Does querying > the current value require sudo? > No, does not appear to need sudo to read: $ sysctl kern.maxvnodes kern.maxvnodes: 524288 (There's also `sysctl -a` to print all the n

Re: moz.build processing time

2016-11-24 Thread Mike Hommey
On Thu, Nov 24, 2016 at 07:04:33PM -0500, Nathan Froyd wrote: > On Wed, Nov 23, 2016 at 4:31 PM, Mike Hommey wrote: > > I know OSX can be bad with I/O, but that seems unusually bad. IIRC gps > > found that there's a relatively low limit to the number of files or > > inodes that can be in cache, an

Re: moz.build processing time

2016-11-24 Thread Nathan Froyd
On Wed, Nov 23, 2016 at 4:31 PM, Mike Hommey wrote: > I know OSX can be bad with I/O, but that seems unusually bad. IIRC gps > found that there's a relatively low limit to the number of files or > inodes that can be in cache, and a working tree of m-c alone is close > to the limit, so changing tha

Re: moz.build processing time

2016-11-23 Thread Mike Hommey
On Wed, Nov 23, 2016 at 04:24:25PM -0500, Ehsan Akhgari wrote: > On 2016-11-23 4:09 PM, Mike Hommey wrote: > > On Wed, Nov 23, 2016 at 01:57:44PM -0500, Ehsan Akhgari wrote: > >> Here is mine: > >> > > > > 12.9s spent in 324 calls to

Re: moz.build processing time

2016-11-23 Thread Ehsan Akhgari
On 2016-11-23 4:09 PM, Mike Hommey wrote: > On Wed, Nov 23, 2016 at 01:57:44PM -0500, Ehsan Akhgari wrote: >> Here is mine: >> > > 12.9s spent in 324 calls to select.select. > 4.8s spent in 43898 calls to posix.stat. > > That's an a

Re: moz.build processing time

2016-11-23 Thread Mike Hommey
On Wed, Nov 23, 2016 at 01:57:44PM -0500, Ehsan Akhgari wrote: > Here is mine: > 12.9s spent in 324 calls to select.select. 4.8s spent in 43898 calls to posix.stat. That's an awful lot of time for I/O. It almost looks like you're us

Re: moz.build processing time

2016-11-23 Thread Ehsan Akhgari
On 2016-11-22 7:39 PM, Gregory Szorc wrote: > On Mon, Nov 21, 2016 at 2:06 PM, Ehsan Akhgari > wrote: > > On 2016-11-21 1:08 PM, Gregory Szorc wrote: > > On Sat, Nov 19, 2016 at 1:32 PM, Ehsan Akhgari > >

Re: moz.build processing time

2016-11-22 Thread Gregory Szorc
On Mon, Nov 21, 2016 at 2:06 PM, Ehsan Akhgari wrote: > On 2016-11-21 1:08 PM, Gregory Szorc wrote: > > On Sat, Nov 19, 2016 at 1:32 PM, Ehsan Akhgari > > wrote: > > > > On 2016-11-19 4:26 PM, Mike Hommey wrote: > > > On Sat, Nov 19, 2016 at 04:12:22PM -05

Re: moz.build processing time

2016-11-21 Thread Ehsan Akhgari
On 2016-11-21 1:08 PM, Gregory Szorc wrote: > On Sat, Nov 19, 2016 at 1:32 PM, Ehsan Akhgari > wrote: > > On 2016-11-19 4:26 PM, Mike Hommey wrote: > > On Sat, Nov 19, 2016 at 04:12:22PM -0500, Ehsan Akhgari wrote: > >> On 2016-11-18 7:22 PM, Gregory Sz

Re: moz.build processing time

2016-11-21 Thread Gregory Szorc
On Sat, Nov 19, 2016 at 1:32 PM, Ehsan Akhgari wrote: > On 2016-11-19 4:26 PM, Mike Hommey wrote: > > On Sat, Nov 19, 2016 at 04:12:22PM -0500, Ehsan Akhgari wrote: > >> On 2016-11-18 7:22 PM, Gregory Szorc wrote: > >>> On Fri, Nov 18, 2016 at 3:50 PM, Ehsan Akhgari < > ehsan.akhg...@gmail.com >

Re: moz.build processing time

2016-11-19 Thread Ehsan Akhgari
On 2016-11-19 4:26 PM, Mike Hommey wrote: > On Sat, Nov 19, 2016 at 04:12:22PM -0500, Ehsan Akhgari wrote: >> On 2016-11-18 7:22 PM, Gregory Szorc wrote: >>> On Fri, Nov 18, 2016 at 3:50 PM, Ehsan Akhgari >> > wrote: >>> >>> Here are the moz.build processing time

Re: moz.build processing time

2016-11-19 Thread Mike Hommey
On Sat, Nov 19, 2016 at 04:12:22PM -0500, Ehsan Akhgari wrote: > On 2016-11-18 7:22 PM, Gregory Szorc wrote: > > On Fri, Nov 18, 2016 at 3:50 PM, Ehsan Akhgari > > wrote: > > > > Here are the moz.build processing times on my machine when I add one > > line

Re: moz.build processing time

2016-11-19 Thread Ehsan Akhgari
On 2016-11-18 7:22 PM, Gregory Szorc wrote: > On Fri, Nov 18, 2016 at 3:50 PM, Ehsan Akhgari > wrote: > > Here are the moz.build processing times on my machine when I add one > line to a LOCAL_INCLUDES in one moz.build file: > > 0:02.97 Reticulating s

Re: moz.build processing time

2016-11-18 Thread Gregory Szorc
On Fri, Nov 18, 2016 at 3:50 PM, Ehsan Akhgari wrote: > Here are the moz.build processing times on my machine when I add one > line to a LOCAL_INCLUDES in one moz.build file: > > 0:02.97 Reticulating splines... > 0:37.16 Finished reading 3131 moz.build files in 23.09s > 0:37.16 Processed into

moz.build processing time

2016-11-18 Thread Ehsan Akhgari
Here are the moz.build processing times on my machine when I add one line to a LOCAL_INCLUDES in one moz.build file: 0:02.97 Reticulating splines... 0:37.16 Finished reading 3131 moz.build files in 23.09s 0:37.16 Processed into 9325 build config descriptors in 3.62s 0:37.16 RecursiveMake backe