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 backend executed in 6.50s 0:37.16 2951 total backend files; 0 created; 2 updated; 2949 unchanged; 0 deleted; 54 -> 1110 Makefile 0:37.16 FasterMake backend executed in 0.50s 0:37.16 12 total backend files; 0 created; 0 updated; 12 unchanged; 0 deleted 0:37.16 Total wall time: 34.22s; CPU time: 16.20s; Efficiency: 47%; Untracked: 0.50s 0:37.89 Finished reading 3131 moz.build files in 21.90s 0:37.89 Processed into 9327 build config descriptors in 3.82s 0:37.89 RecursiveMake backend executed in 7.85s 0:37.89 2951 total backend files; 0 created; 4 updated; 2947 unchanged; 0 deleted; 54 -> 1110 Makefile 0:37.89 FasterMake backend executed in 0.59s 0:37.89 12 total backend files; 0 created; 0 updated; 12 unchanged; 0 deleted 0:37.89 Total wall time: 34.70s; CPU time: 17.70s; Efficiency: 51%; Untracked: 0.55s The clear offender is "reading moz.build files". What's involved in this process? Is there some low hanging fruit for making it faster? Are there things non-build developers can do (such as reducing the number of moz.build files) that would help? Is there any way for us to avoid reprocessing the world for every single moz.build file change? Thanks, Ehsan _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
