Revert "Remove memoryAblationMetric"

This reverts commit 7caeed04db1c5cf0ef6a6ba6351286a33a9a4aff.

Reason for revert: Causing all loading and system_health benchmarks to fail crbug.com/1190611

Original change's description:
> Remove memoryAblationMetric
>
> Our team ran a Finch trial, ending in December 2020, which performed ablation of GPU Memory.
>
> To determine what portion of regressions seen were caused by the ablation itself we added 'memoryAblationMetric'. With the experiment done, this is no longer needed.
>
> The usage in rendering.py is being removed: https://chromium-review.googlesource.com/c/chromium/src/+/2775243/
>
> Bug: chromium:908462
> Change-Id: I97a7c5f2cdee1bd042c5814fe414f2744a25fb4f
> Reviewed-on: https://chromium-review.googlesource.com/c/catapult/+/2774560
> Reviewed-by: Deep Roy <dproy@chromium.org>
> Commit-Queue: Jonathan Ross <jonross@chromium.org>

Bug: chromium:908462, chromium:1190611
Change-Id: I19468bf6461c1e325b92cb5e794892e1af949316
Reviewed-on: https://chromium-review.googlesource.com/c/catapult/+/2776744
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: John Chen <johnchen@chromium.org>
3 files changed
tree: 0b852fbbec2b74a9f2449396922cd188307361bb
  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. generate_telemetry_build.py
  29. LICENSE
  30. navbar.md
  31. OWNERS
  32. PRESUBMIT.py
  33. pylintrc
  34. README.md
  35. 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