New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 798371 link

Starred by 1 user
Status: WontFix
Owner:
yangguo@chromium.org
Closed: Jan 2018
Cc:
mlippautz@chromium.org
yangguo@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.8% regression in rasterize_and_record_micro.top_25 at 526221:526229

Project Member Reported by alexclarke@chromium.org, Jan 2 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 2 2018 

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

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


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

chromium-rel-win10
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 2 2018

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

Remove unused statistic collection code.
By yangguo@chromium.org · Fri Dec 22 08:58:47 2017
v8 @ a7c85f33c14321324301b645507ea90a3322c167

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

Comment 4 by sullivan@chromium.org, Jan 25 2018 

yangguo: Looks like this reverts an earlier improvement, probably in this v8 range: https://chromium.googlesource.com/v8/v8/+log/6a2793267d5fbbbce27d5dbfc9f7285fd620176a..cead990c6ab1ccd06875c5737ac10104ccb785b1

Is this expected? if so, can you mark WontFix?

Comment 5 by yangguo@chromium.org, Jan 25 2018

Status: WontFix (was: Assigned)
Not sure whether we could just interpret that as noise. The commits in the V8 range do not look suspicious.
►

Sign in to add a comment