commit | a297a083906f01f30d435131c0976bfd09ea9c12 | [log] [tgz] |
---|---|---|
author | Jonathan Ross <jonross@chromium.org> | Thu Mar 25 14:14:36 2021 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Mar 25 18:25:52 2021 |
tree | 6bfc43336f289130c1996ef01d2e7baf51ecafe0 | |
parent | 3891e3620c99be4cc8fe8bd900df31e039481fd8 [diff] |
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>
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.
Please see our contributor's guide