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

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


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

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2
chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release
win-high-dpi

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

Associated CL (the nice revert part) https://chromium.googlesource.com/v8/v8/+/1b9e9bb9abeb58135364db117b185d81c6cb5a87

Awesome, so now we have precise data that SlicedStrings are a net win!

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_news/browse_news_nytimes

Revision             Result                  N
chromium@513414      8.2359 +- 13.3327       21      good
chromium@513466      8.45181 +- 13.9355      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.nytimes v8.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection