Issue metadata
Sign in to add a comment
|
chromeos-chrome can take ~1 hour to build on PFQ and Release builders |
||||||||||||||||||||||
Issue descriptionExtracted from issue 896037 Building chromeos-chrome for cyan took 56 minutes in a recent PFQ run: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8931206130574432288 And 51 minutes in a recent release build: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8931067522101960896 Unfortunately there are no additional details in the logs. The long build times especially impact the cycle time on the PFQ. The logs show that USE_GOMA=true. By comparison, the TestSimpleChromeWorkflow stage which builds chrome incrementally in Simple Chrome (cros chrome-sdk) takes about 12 minutes.
,
Nov 5
,
Nov 8
,
Nov 8
I can take ownership of this. There are some improvements planned. - Use of thinlto internal cache (beginning Q1) - Use of goma for backends (Q2?) - build compiler with AFDO to improve speed of toolchain (beginning of Q1) However, we will never reach the time of the simple chrome workflow since simple chrome is not built with thinlto.
,
Nov 8
I don't think we need to make "as fast as Simple Chrome" a goal, but if we can get the build times closer to 30 minutes than 60, that would be a huge win. Thanks for looking into this!
,
Jan 17
(6 days ago)
I got pinged about the status of this: - Use of thinlto internal cache (should be coming soon after Jan 24 - branch point). - build compiler with AFDO to improve speed of toolchain (should be done by the end of Q1) - Use GOMA for backends will not be done this quarter. Probably Q3 or Q4. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by steve...@chromium.org
, Nov 1