New issue
Advanced search Search tips

Issue 857084 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 13
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.9% regression in thread_times.key_silk_cases at 568128:568271

Project Member Reported by nzolghadr@chromium.org, Jun 27 2018

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

android-nexus5
Project Member

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

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

Adjust the edge-AA tessellator maximum verb count. by senorblanco@chromium.org
https://chromium.googlesource.com/chromium/src/+/df18b96b443774d232e39ead6cbd81c848b8563c
73.05 → 76.3 (+3.256)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
The first two graphs above have recovered after Skia https://skia.googlesource.com/skia/+/2272ea2a4bcd3cd16547eeb8e0902d9b06ea26b4, rolled into Chrome at r574747. The last one has not, but we can live with this regression for the gains we see on other benchmarks.

https://chromeperf.appspot.com/report?sid=c5f4add8edfd6761d93278432f7b4c4e7f2e5b8f5b3b1bb8d8a379eb2a53539c
Status: Fixed (was: Assigned)

Sign in to add a comment