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

Issue 777508 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
█ pmeenan@chromium.org
h...@chromium.org
thakis@chromium.org
r...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

5.5%-15.7% regression in sizes at 510823:510824

Project Member Reported by pmeenan@chromium.org, Oct 23 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 23 2017 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=777508

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=a34c465d5bb532a376b15130882d7ea9eff37121c203730d5a0b4a4fb3c91bef


Bot(s) for this bug's original alert(s):

win-32

Comment 2 by thestig@chromium.org, Dec 22 2017

Cc: h...@chromium.org thakis@chromium.org
Components: Build
Labels: -Pri-2 clang OS-Windows Pri-1
pmeenan: 15% regression is 51 MB -> 59 MB for chrome_child.dll. Was someone suppose to follow up on untriaged bugs with the Performance-Sheriff label?

This is a big size regression from enabling Clang in r510824. Has this been discussed?

Comment 3 by thestig@chromium.org, Dec 22 2017

Cc: r...@chromium.org

Comment 4 by h...@chromium.org, Dec 22 2017

Status: WontFix (was: Untriaged)
Yes, the size increase for 32-bit Chrome was expected. The compressed size (mini_installer.exe) was not affected as much, and on 64-bit the size was reduced.

We compared the mini_installer.exe sizes for 64.0.3278.0/2:

  win-pgo     45.46 MB
  win64-pgo   49.40 MB
  win-clang   45.65 MB (+0.04%)
  win64-clang 46.27 MB (-6.33%)
►

Sign in to add a comment