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

Issue 868045 link

Starred by 1 user
Status: WontFix
Owner:
clemensh@chromium.org
Closed: Aug 1
Cc:
█ ushesh@chromium.org
clemensh@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

26.6% regression in rendering.desktop at 577561:577602

Project Member Reported by ushesh@chromium.org, Jul 26 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 26 

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

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


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

mac-10_13_laptop_high_end-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 26

Cc: clemensh@chromium.org
Owner: clemensh@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14bbf637a40000

[Flags] Explicitly disable Liftoff if tier up is disabled by clemensh@chromium.org
https://chromium.googlesource.com/chromium/src/+/fab5510cbf8165739f2d228ba6d4c25c5b5530f8
29.2 → 38.52 (+9.326)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 4 by clemensh@chromium.org, Aug 1

Status: WontFix (was: Assigned)
This CL fixes wrong behaviour if the "enable-webassembly-baseline" flag is disabled. The regression we see here just restores the old behavior of compiling with Turbofan instead of Liftoff.
►

Sign in to add a comment