New issue
Advanced search Search tips

Issue 895361 link

Starred by 1 user
Status: Duplicate
Merged: issue 895360
Owner:
r...@igalia.com
Closed: Oct 16
Cc:
npm@chromium.org
r...@igalia.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10.9% regression in rendering.mobile/tasks_per_frame_total_all at 598969:599042

Project Member Reported by npm@chromium.org, Oct 15 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 15 

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

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


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

android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 15

Cc: r...@igalia.com
Owner: r...@igalia.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12cec442e40000

Fix perf regression in LayoutBoxModelObject::RelativePositionOffset() by rego@igalia.com
https://chromium.googlesource.com/chromium/src/+/4226ddf99103e493d7afb23a4c7902ee496108b6
tasks_per_frame_total_all: 65.82 → 73.24 (+7.424)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 4 by r...@igalia.com, Oct 16

Mergedinto: 895360
Status: Duplicate (was: Assigned)
This seems the same than  issue #895360 .
►

Sign in to add a comment