New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 599882 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Remove Syzygy step from the official builders, clean-up archive step

Project Member Reported by lafo...@chromium.org, Apr 1 2016

Issue description

Post XP/Vista deprecation we are likely no longer realizing a benefits from Syzygy, so it would be good to remove that step (both to recapture the time in the build process and reduce build flake).

 
Labels: -M-51 M-52

Comment 2 by mmoss@chromium.org, Apr 14 2016

Cc: chrome-release-team@google.com

Comment 3 by tin...@google.com, Apr 16 2016

Labels: Proj-Nightfall
Owner: fdoray@chromium.org
Status: Assigned (was: Untriaged)
The first step in this process is double checking that the step is no longer required. fdoray@ has volunteered to make this one of this series of startup optimization experiments. Assigning to him to track this for now.
Project Member

Comment 5 by bugdroid1@chromium.org, Apr 22 2016

The following revision refers to this bug:
  http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=86935

------------------------------------------------------------------
r86935 | fdoray@google.com | 2016-04-22T15:02:08.705030Z

-----------------------------------------------------------------

Comment 6 by fdoray@chromium.org, Apr 22 2016

Plan to assess the impact of Syzygy on startup time:

1. Add a 'noop' flag to syzygy_optimize.py. When this flag is set, the script will just copy chrome.packed.7z from out\Release to out\Release\syzygy (the script already does that for clang builds).
2. Trigger a Dev build.
3. Set the 'noop' flag in AddSyzygyOptimizeStep.
4. Update the buildspec for the branch from which the Dev build was triggered so that it uses the latest build scripts.
5. Trigger a second Dev build.
6. Revert the change made in step 3.
7. Ship the first build to 50% of users and the other one to the other half.
8. Compare startup histograms for the two dev builds.

Project Member

Comment 7 by bugdroid1@chromium.org, May 4 2016

The following revision refers to this bug:
  http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=87390

------------------------------------------------------------------
r87390 | fdoray@google.com | 2016-05-04T15:13:05.729369Z

-----------------------------------------------------------------
Project Member

Comment 8 by bugdroid1@chromium.org, May 5 2016

The following revision refers to this bug:
  http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=87449

------------------------------------------------------------------
r87449 | fdoray@google.com | 2016-05-05T14:10:09.527224Z

-----------------------------------------------------------------

Comment 9 by fdoray@chromium.org, May 17 2016

Status: Fixed (was: Assigned)

Sign in to add a comment