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

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


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

chromium-rel-win10

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

=== Auto-CCing suspected CL author gsathya@chromium.org ===

Hi gsathya@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Sathya Gunasekaran
  Commit : 01c82f9cab010b390f9ad15de9edf1fee44b972e
  Date   : Mon Aug 21 05:30:01 2017
  Subject: Reland "[runtime] Store hash code in length field"

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : memory.desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/TrivialScrollingPageSharedPageState
  Change       : 5.62% | 9326592.0 -> 9850880.0

Revision                           Result              N
chromium@495918                    9326592 +- 0.0      6      good
chromium@495921                    9326592 +- 0.0      6      good
chromium@495922                    9326592 +- 0.0      6      good
chromium@495922,v8@01c82f9cab      9850880 +- 0.0      6      bad       <--
chromium@495922,v8@1e08466b76      9850880 +- 0.0      6      bad
chromium@495922,v8@21183dd19c      9850880 +- 0.0      6      bad
chromium@495923                    9850880 +- 0.0      6      bad
chromium@495927                    9850880 +- 0.0      6      bad
chromium@495935                    9850880 +- 0.0      6      bad
chromium@495952                    9850880 +- 0.0      6      bad
chromium@495985                    9850880 +- 0.0      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=TrivialScrollingPageSharedPageState memory.desktop

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

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


For feedback, file a bug with component Speed>Bisection

gsathya, any update on this bug? It's showing a 500kib regression at your CL.

Looks it recovered this particular regression?

Ah, sorry, looks like it did.