New issue
Advanced search Search tips

Issue 896320 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.1%-9.8% regression in cpu_time_percentage,memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size at 599655:599835

Project Member Reported by 42576172...@developer.gserviceaccount.com, Oct 17

Issue description

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

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


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

Win 7 Perf
linux-perf

system_health.common_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

memory.desktop - Benchmark documentation link:
  None

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

Downloads: After 100 numerically deduplicated files, try timestamp by tommycli@chromium.org
https://chromium.googlesource.com/chromium/src/+/e40c631a5f311d449e8c6e136f0d70e5d548b987
cpu_time_percentage: 0.2892 → 0.3163 (+0.02714)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

Sign in to add a comment