New issue
Advanced search Search tips

Issue 880929 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 7
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.5% regression in blink_perf.canvas at 588439:588442

Project Member Reported by sullivan@chromium.org, Sep 5

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=880929

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


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

mac-10_12_laptop_low_end-perf

blink_perf.canvas - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Cc: bmeu...@chromium.org
Owner: bmeu...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16fee5f5640000

[turbofan] Be more consistent about Smi comparisons. by bmeurer@chromium.org
https://chromium.googlesource.com/v8/v8/+/0aac3884c9e02b34861d526d2d5c62f8628483f3
888.7 → 788.2 (-100.5)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Status: WontFix (was: Assigned)
This is a micro-benchmark where the previous heuristics seems to be beneficial. Still better to be consistent here.

Sign in to add a comment