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

Issue 855397 link

Starred by 1 user
Status: Assigned
Owner:
japhet@chromium.org
Cc:
japhet@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11.1% regression in system_health.memory_desktop at 565366:565528

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

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

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

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

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

Merge HistoryCommitType and WebHistoryCommitType, and remove a value by japhet@chromium.org
https://chromium.googlesource.com/chromium/src/+/e83e9f9b6e3d775873ef6ee1b98b41a77425a4e9
4.174e+07 → 4.731e+07 (+5.578e+06)

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

Comment 4 by benhenry@chromium.org, Aug 2

Components: Speed>Metrics>SystemHealthRegressions

Comment 5 by benhenry@chromium.org, Aug 2

Components: -Speed>Metrics>SystemHealthRegressions
►

Sign in to add a comment