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

Issue 880274 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 868909
Owner:
OOO Dec 22 - Jan 8
Closed: Sep 6
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-4.2% regression in memory.desktop at 588371:588386

Project Member Reported by maxlg@chromium.org, Sep 4

Issue description

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

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


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

linux-perf
mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

memory.desktop - Benchmark documentation link:
  None

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: olka@chromium.org
Owner: olka@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11879859640000

Restoring field trial config for AudioService experiment on linux/mac by olka@chromium.org
https://chromium.googlesource.com/chromium/src/+/7ec94d0b3562d9414f716a1d6cb711d2fcf12c2f
2.939e+07 → 3.063e+07 (+1.244e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 868909
Status: Duplicate (was: Assigned)

Sign in to add a comment