Difference between revisions of "Profile the build system"
(→Project Details) |
(→Project Details) |
||
| Line 37: | Line 37: | ||
! style="background:#efefef;" colspan="2" | without -j4 | ! style="background:#efefef;" colspan="2" | without -j4 | ||
! style="background:#efefef;" colspan="3" | Hardware | ! style="background:#efefef;" colspan="3" | Hardware | ||
| + | ! style="background:#efefef;" rowspan="2" | Apps opened while building | ||
! style="background:#efefef;" rowspan="2" | OS | ! style="background:#efefef;" rowspan="2" | OS | ||
! style="background:#efefef;" rowspan="2" | User | ! style="background:#efefef;" rowspan="2" | User | ||
| Line 55: | Line 56: | ||
| 2.0 GHz Duo | | 2.0 GHz Duo | ||
| 7200 | | 7200 | ||
| + | | None | ||
| Vista | | Vista | ||
| [[User:Pplam3|Patrick]] | | [[User:Pplam3|Patrick]] | ||
| Line 64: | Line 66: | ||
| 1 GB | | 1 GB | ||
| 1.6 GHz Duo | | 1.6 GHz Duo | ||
| + | | | ||
| | | | ||
| XP Media | | XP Media | ||
Revision as of 13:29, 18 September 2008
Contents
Name of Project
Profile the build system
Description
It's a well known fact that it takes longer to build on Windows than on a comparable Linux or Mac machine. We don't know exactly why, however. There have been many theories, but no real data. Profiling the build system would allow us to figure out where all of the time is being spent. The best place to start might be by adding some profiling to GNU Make, to figure out which targets in our makefiles take the most time. From there, depending on the results, profiling could be added to other parts of the build system to narrow down specific bottlenecks.
References:
- http://wiki.services.openoffice.org/wiki/BuildSpeedup - OpenOffice.org did something similar
Resources: ted
Leader(s)
Project Contributor(s)
Project Details
- Collect Data
- Get build time info from others
- Build From Scratch, Rebuild with no changes, using/not using -j4 option, hardware info (RAM, CPU, RPM)
- Get build time info from others
- The -j4 option is to be put in the .mozconfig file
- -j specifies how many concurrent jobs you can run, so for some parts of the tree you get more makaes going at once
- mk_add_options MOZ_MAKE_FLAGS=-j4
- Please feel free to fill in the table to help me collect more data
- YOU WILL BE CONSIDER A PROJECT CONTRIBUTOR FOR PROVIDING DATA
| with -j4 | without -j4 | Hardware | Apps opened while building | OS | User | ||||
|---|---|---|---|---|---|---|---|---|---|
| Build From Scratch | Rebuilt No Changes | Build From Scratch | Rebuilt No Changes | RAM | CPU | HD (rpm) | |||
| 0:59:00 | 0:21:00 | 4 GB | 2.0 GHz Duo | 7200 | None | Vista | Patrick | ||
| 1:03:00 | 1 GB | 1.6 GHz Duo | XP Media | Tony | |||||
Project News / Updates
09/18/2008 -
- Use time command to time build time
- ie. time make -f client.mk build
09/17/2008 -
- Built the first time in 1h 20m
- Rebuilt second time in 35m with all apps off
- Talked with Shaver and directed me to thread on shrinking build time
- Thread talked about /MP command for building in VS -> not useful in my case
- Dave's suggestion
- Understand what each part of the build is taking
- Collect win32 build times from colleagues
09/16/2008 -
- Talked with Ted Mielczarek, briefly discussed about where to start and how to approach this project.
- Start by timing how long each make file is
- Identify which make file takes a long time
09/15/2008 -
- Created Project page for this project.
