Reland "Remove memoryAblationMetric"

As a follow-up to the initial removal of "memoryAblationMetric" I have went back and removed the other references within other benchmarks: https://chromium-review.googlesource.com/c/chromium/src/+/2785903

Locally I re-ran rendering, loading, and system_health metrics to confirm the crash was not reproducing anymore.

This patch is a direct reland, no edits after the revert of the revert.

Original patch reviewed: https://chromium-review.googlesource.com/c/catapult/+/2774560

Revert "Revert "Remove memoryAblationMetric""

This reverts commit 999f35f30e7ed72d640fea1b86f74d54a41896ed.

Bug: chromium:908462, chromium:1190611
Change-Id: I8e18c6145a28aff397afdf28f1bb29293e5e4655
Reviewed-on: https://chromium-review.googlesource.com/c/catapult/+/2785567
Reviewed-by: Deep Roy <dproy@chromium.org>
Commit-Queue: Jonathan Ross <jonross@chromium.org>
3 files changed
tree: 6bfc43336f289130c1996ef01d2e7baf51ecafe0
  1. bin/
  2. catapult_build/
  3. common/
  4. dashboard/
  5. dependency_manager/
  6. devil/
  7. docs/
  8. experimental/
  9. firefighter/
  10. hooks/
  11. infra/
  12. netlog_viewer/
  13. systrace/
  14. telemetry/
  15. third_party/
  16. trace_processor/
  17. tracing/
  18. web_page_replay_go/
  19. .eslintignore
  20. .eslintrc
  21. .gcloudignore
  22. .gitignore
  23. .vpython
  24. AUTHORS
  25. BUILD.gn
  26. codereview.settings
  27. CONTRIBUTING.md
  28. DIR_METADATA
  29. generate_telemetry_build.py
  30. LICENSE
  31. navbar.md
  32. OWNERS
  33. PRESUBMIT.py
  34. pylintrc
  35. README.md
  36. WATCHLISTS
README.md

Catapult

Catapult is the home for several performance tools that span from gathering, displaying and analyzing performance data. This includes:

These tools were created by Chromium developers for performance analysis, testing, and monitoring of Chrome, but they can also be used for analyzing and monitoring websites, and eventually Android apps.

Contributing

Please see our contributor's guide