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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkrbhtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkrngvAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkpbNsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkqG2uwoM


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

chromium-rel-win7-single

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9007168752183835168

It could be because of this (https://codereview.chromium.org/2067793004/). In this benchmark we collect periodic light memory dumps and two heavy dumps. Telemetry could only handle one request at a time, so some of the requests were dropped when another dump was in progress. Petr fixed it and the results are more stable after that point. If we look at the dump_count or dump_count:detailed, we can see the raise in the same range. So I think this is not a real regression, it is just more accurate results.

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@401842  14258277  1900188  18  good
chromium@401996  14044416  2338825  18  bad

Bisect job ran on: win_perf_bisect
Bug ID: 628171

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests top_10_mobile_memory_ignition
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/http___m.youtube.com_results?q_science
Relative Change: 5.05%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6693
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007168752183835168


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4640677825085440

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!