New issue
Advanced search Search tips

Issue 849280 link

Starred by 1 user
Status: Assigned
Owner:
erikc...@chromium.org
Cc:
fmeawad@google.com
erikc...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.2% regression in tracing_perftests at 561956:562040

Project Member Reported by fmea...@chromium.org, Jun 4 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 4 2018 

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

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


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

linux-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 4 2018

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

Remove dead code for legacy heap profiler. by erikchen@chromium.org
https://chromium.googlesource.com/chromium/src/+/f62ea04b8e2b89eb110b1615c905fa8ffdb3b90d
20 → 21.2 (+1.2)

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

Comment 4 by erikc...@chromium.org, Jun 4 2018 

My CL removes a lot of dead code. Not sure how this could trigger a perf regression.
►

Sign in to add a comment