New issue
Advanced search Search tips

Issue 816541 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 816492

Blocking:
issue 812178



Sign in to add a comment

Diagnose impact of v8:51458

Project Member Reported by gab@chromium.org, Feb 26 2018

Issue description

If you are assigned this bug, I'm sorry, I'm running a bunch of pinpoint jobs and it doesn't yet support not auto-assigning... (please re-assign to gab@ in that event).

Benchmarks affected by increasing the number of workers contributing to concurrent marking coalesced @
https://chromeperf.appspot.com/group_report?bug_id=816541

as well as lost ~2.5% on chromium-rel-win10/octane/Splay (visible even though too noisy to generate a linkable alert): https://chromeperf.appspot.com/report?sid=58d57db8b3635bfe30dc64e4a48dca7972ba2bffbb8d429e43dcd1e807e8d866&start_rev=534293&end_rev=539114

Many graphs in this report can be seen to improve as well (no alerts generated because it followed a big spike and the stddev necessary for an alert temporarily increased...): https://chromeperf.appspot.com/group_report?bug_id=809961 (this report captures the graphs which regressed initially in related r534414 -- subsequently fixed in v8:r51249)

Noteworthy above: v8-gc-total_sum / v8-gc-full-mark-compactor_avg
 
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Feb 26 2018

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

Comment 8 by 42576172...@developer.gserviceaccount.com, Feb 26 2018

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

Comment 9 by 42576172...@developer.gserviceaccount.com, Feb 26 2018

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

Comment 10 by 42576172...@developer.gserviceaccount.com, Feb 26 2018

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

Comment 11 by 42576172...@developer.gserviceaccount.com, Feb 26 2018

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

Comment 12 by 42576172...@developer.gserviceaccount.com, Feb 26 2018

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/174cfb20440000

Comment 13 by gab@chromium.org, Feb 27 2018

Blockedon: 816544

Comment 14 by gab@chromium.org, Feb 27 2018

Blockedon: 816492
Project Member

Comment 23 by 42576172...@developer.gserviceaccount.com, Feb 27 2018

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

Comment 24 by 42576172...@developer.gserviceaccount.com, Feb 27 2018

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

Comment 25 by 42576172...@developer.gserviceaccount.com, Feb 27 2018

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14a76f08440000
Project Member

Comment 26 by 42576172...@developer.gserviceaccount.com, Feb 27 2018

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14bd3af0440000
Project Member

Comment 27 by 42576172...@developer.gserviceaccount.com, Feb 27 2018

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/12c92598440000
Project Member

Comment 28 by 42576172...@developer.gserviceaccount.com, Feb 27 2018

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14b98668440000
Project Member

Comment 29 by 42576172...@developer.gserviceaccount.com, Feb 27 2018

Cc: gab@chromium.org u...@chromium.org mlippautz@chromium.org v8-autoroll@chromium.org
Status: Assigned (was: Started)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/16a80cd8440000

Use all available workers for concurrent marking. by gab@chromium.org
https://chromium.googlesource.com/v8/v8/+/3c62f7ae0744ebf95769429e5b2b3c83fc384fdf

Revert "Update V8 to version 6.6.283." by gab@chromium.org
https://chromium.googlesource.com/chromium/src/+/7de67f111bbb38a270e02e44e5d99d5baa355d76

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

Comment 30 by 42576172...@developer.gserviceaccount.com, Feb 27 2018

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

Use all available workers for concurrent marking. by gab@chromium.org
https://chromium.googlesource.com/v8/v8/+/3c62f7ae0744ebf95769429e5b2b3c83fc384fdf

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

Comment 33 by gab@chromium.org, Feb 28 2018

Description: Show this description

Comment 34 by gab@chromium.org, Feb 28 2018

Blockedon: -816544

Comment 35 by gab@chromium.org, Feb 28 2018

Description: Show this description

Comment 36 by gab@chromium.org, Feb 28 2018

Blocking: 812178

Comment 37 by gab@chromium.org, Feb 28 2018

Status: Fixed (was: Assigned)
Alright I think I've coalesced all the effects of this CL.

It improves so system_health.memory_desktop benchmarks, some Group-GC/duration stats, and Splay for nodejs.

Interestingly, tt regresses Splay on mac11-pro and win10-rel however.

Graphs : https://chromeperf.appspot.com/group_report?bug_id=816541

+ win10-rel/Splay : https://chromeperf.appspot.com/report?sid=58d57db8b3635bfe30dc64e4a48dca7972ba2bffbb8d429e43dcd1e807e8d866&start_rev=534293&end_rev=539114
Project Member

Comment 38 by 42576172...@developer.gserviceaccount.com, Feb 28 2018

Cc: rsesek@chromium.org thestig@chromium.org w...@chromium.org
Owner: w...@chromium.org
Status: Assigned (was: Fixed)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/17a87268440000

Fix CreateAnonymousSharedMemory() not to leak FILE when returning fd. by wez@chromium.org
https://chromium.googlesource.com/chromium/src/+/45a7b305282b175e11c871c1a8ac3b8336c66259

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

Comment 39 by gab@chromium.org, Feb 28 2018

Cc: -rsesek@chromium.org -w...@chromium.org -thestig@chromium.org
Owner: gab@chromium.org
Congrats Wez! Created  issue 817356  to document your improvement.
Project Member

Comment 40 by 42576172...@developer.gserviceaccount.com, Feb 28 2018

Cc: jvanverth@google.com robertph...@google.com
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1498e278440000

Revert "Revert "Separate creation time & flush time behavior in GrDrawOpAtlas (take 2)"" by robertphillips@google.com
https://skia.googlesource.com/skia/+/934c3d0c548d254a0d986963ee751caf0ffcb500

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

Comment 41 by gab@chromium.org, Mar 1 2018

Description: Show this description

Comment 42 by gab@chromium.org, Mar 1 2018

Description: Show this description
Cc: -robertph...@google.com

Comment 44 by gab@chromium.org, Mar 1 2018

Cc: -jvanverth@google.com simonhatch@chromium.org
@simonhatch, see OP, we have many graphs on which we see improvements/regressions which we would like to tag to this bug but we can't because no automatic alert was detected (in general because the relevant metrics experienced an unrelated spike during the improvement, increasing the stddev and hiding everything else within).

Is there any way we can manually add an "alert" point and link it to this bug?
Cc: benjhayden@chromium.org
re: #c44

No there's no way to manually create an alert at the moment. If this is high priority, I could rig something up for you, otherwise this is a requested feature for the new UI that benjhayden@ is working on.
Project Member

Comment 46 by bugdroid1@chromium.org, Mar 2 2018

Comment 48 by gab@chromium.org, May 4 2018

Status: Fixed (was: Assigned)

Sign in to add a comment