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: > >> <https://gist.github.com/ehsan/ad4e56f2d2f70e3e6c578a2517afbc15> > > > > 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 using a > > good old spinning disk. > > Fairly certain it's an SSD, but it must be a pretty crappy one. At any > rate this is Apple hardware which is pretty common at MoCo as you know. :(
Well, if you run mach build-backend multiple times in a row and times don't change, then it would be an OS thing rather than a hardware thing. Because the second time, everything should be in memory. 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 that configuration could help. Greg, do you remember what it is? Other than that, I'd suggest getting a profile through XCode's Instruments. Mike _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
