New issue
Advanced search Search tips

Issue 829850 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-1.6% regression in thread_times.tough_compositor_cases at 547841:547969

Project Member Reported by primiano@chromium.org, Apr 6 2018

Issue description

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

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


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

chromium-rel-mac11-pro
chromium-rel-mac12
 Issue 829849  has been merged into this issue.
 Issue 829848  has been merged into this issue.
 Issue 829847  has been merged into this issue.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Apr 13 2018

Cc: tsepez@chromium.org thestig@chromium.org khushals...@chromium.org oksamyt@chromium.org enne@chromium.org
Owner: oksamyt@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/15e6f5c2c40000

cc: Issue tile manager signals synchronously by enne@chromium.org
https://chromium.googlesource.com/chromium/src/+/618a8341cb195e8c26bc954ae013aa2fde557411

Convert cloud_print.mojom to use mojo/public/mojom/base/values.mojom by oksamyt@chromium.org
https://chromium.googlesource.com/chromium/src/+/dd936623555c9564d188e67fb193ccf552f46f62

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

Comment 10 by 42576172...@developer.gserviceaccount.com, Apr 13 2018

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/11e935eac40000
Project Member

Comment 12 by 42576172...@developer.gserviceaccount.com, Apr 13 2018

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/178ad31cc40000

cc: Issue tile manager signals synchronously by enne@chromium.org
https://chromium.googlesource.com/chromium/src/+/618a8341cb195e8c26bc954ae013aa2fde557411

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

Comment 13 by 42576172...@developer.gserviceaccount.com, Apr 13 2018

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15fb3062c40000

cc: Issue tile manager signals synchronously by enne@chromium.org
https://chromium.googlesource.com/chromium/src/+/618a8341cb195e8c26bc954ae013aa2fde557411

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

Comment 14 by 42576172...@developer.gserviceaccount.com, Apr 13 2018

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16adc7b2c40000
Owner: ----
Status: Available (was: Assigned)
According to Pinpoint, there are differences in performance between revisions 547954 and 547955 (by enne@) and no differences between revisions 547965 and 547966 (by me). I will unassign myself from this ticket, please let me know if any further action is required.

Comment 16 by enne@chromium.org, Apr 16 2018

Status: WontFix (was: Available)
This is quite small and cleans up some complicated code.  It does not makes sense to me why this would be a performance regression (calling a function instead of posting it).

I'm going to WontFix it.

Sign in to add a comment