New issue
Advanced search Search tips

Issue 873392 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.5%-15.8% regression in blink_perf.shadow_dom at 581004:581340

Project Member Reported by lanwei@chromium.org, Aug 10

Issue description

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

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


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

Android Nexus5 Perf
mac-10_12_laptop_low_end-perf
Components: -Blink>JavaScript Blink>Bindings Blink>DOM>ShadowDOM
This looks a real regression.
To Performance-Sheriff, could you have a chance to triage?
Cc: mlippautz@chromium.org
Owner: mlippautz@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13c52e72640000

[bindings,heap] Prepare PerIsolateData for holding different heap tracer by mlippautz@chromium.org
https://chromium.googlesource.com/chromium/src/+/1186c664d583e43a45f365d4a5291bed032542bd
7.844 → 8.74 (+0.896)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Cc: -mlippautz@chromium.org
Status: Fixed (was: Assigned)
Got reverted here: https://chromium-review.googlesource.com/c/chromium/src/+/1170743

Sign in to add a comment