New issue
Advanced search Search tips

Issue 896827 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 896328
Owner:
Closed: Oct 18
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

222.1%-373.7% regression in complex-iframe-filtered at 600027:600102

Project Member Reported by 42576172...@developer.gserviceaccount.com, Oct 18

Issue description

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

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

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

Disable iframe isolation nodes via a flag. by vmpstr@chromium.org
https://chromium.googlesource.com/chromium/src/+/eeb3499ace08617926f1d0a7ece1c5f1ed677001
complex-iframe-filtered: 327.2 → 1479 (+1152)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Mergedinto: 896328
Status: Duplicate (was: Assigned)

Sign in to add a comment