New issue
Advanced search Search tips

Issue 770895 link

Starred by 1 user
Status: Duplicate
Merged: issue 770546
Owner:
cmumford@chromium.org
Closed: Oct 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1538.4% regression in LevelDB_memory_dump_cpu_overhead_avg/http___www.yahoo.com_ on android-nexus5 at 501910:504766

Project Member Reported by ssid@chromium.org, Oct 2 2017 
Performance dashboard identified a 1538.4% regression in tracing.tracing_with_background_memory_infra/LevelDB_memory_dump_cpu_overhead_avg/http___www.yahoo.com_ on android-nexus5 at revision range 501910:504766. Graph: https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=android-nexus5&tests=tracing.tracing_with_background_memory_infra%2FLevelDB_memory_dump_cpu_overhead_avg%2Fhttp___www.yahoo.com_&checked=http___www.yahoo.com_%2Chttp___www.yahoo.com__ref%2Cref&rev=504766

There seems to be performance regression of dump time of levelDB provider. This happened in CL range that does not include Enabling the provider. But it includes 3-4 CLs on levelDB env.

Chris, Is this expected? The cpu time of OnMemoryDump() call went from 2ms to 200 ms in some cases.
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 3 2017

Mergedinto: 770546
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Lalit Maganti
  Commit : fdc0a261697b6e767f45acb3d61fb5dc005d205a
  Date   : Thu Sep 21 12:30:10 2017
  Subject: memory-infra: Enable LevelDB global dumps in background mode

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : tracing.tracing_with_background_memory_infra
  Metric       : LevelDB_memory_dump_cpu_overhead_avg/http___www.yahoo.com_
  Change       : 1562.56% | 0.0181078373016 -> 0.301053075397

Revision             Result                       N
chromium@501909      0.0181078 +- 0.0154719       6      good
chromium@503338      0.015595 +- 0.00614152       6      good
chromium@503383      0.0164349 +- 0.00792374      6      good
chromium@503406      0.0292311 +- 0.0916948       6      good
chromium@503417      0.015969 +- 0.00226374       6      good
chromium@503420      0.0178822 +- 0.0213629       6      good
chromium@503421      0.0154158 +- 0.00682504      6      good
chromium@503422      0.297284 +- 0.172792         6      bad       <--
chromium@503423      0.292915 +- 0.114785         6      bad
chromium@503428      0.284962 +- 0.0985863        6      bad
chromium@503517      0.296425 +- 0.171362         6      bad
chromium@503695      0.254425 +- 0.0281726        6      bad
chromium@504052      0.261645 +- 0.0357582        6      bad
chromium@504766      0.301053 +- 0.143537         6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.yahoo.com. tracing.tracing_with_background_memory_infra

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966809640318414304


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment