Ignore forced Blink GCs in metrics

Similar to V8 traces, ignore forced Blink GCs as they can dominate
the results.

Bug: chromium:843903
Change-Id: I6f1760306193cea4b48caa203e0f9c16867f5416
Reviewed-on: https://chromium-review.googlesource.com/c/1269155
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Ben Hayden <benjhayden@chromium.org>
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
2 files changed
tree: f77a42d1c39d273fa682ab362898b6f4e6fc5eaf
  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. .gitignore
  22. .vpython
  23. AUTHORS
  24. BUILD.gn
  25. codereview.settings
  26. CONTRIBUTING.md
  27. generate_telemetry_build.py
  28. LICENSE
  29. navbar.md
  30. OWNERS
  31. PRESUBMIT.py
  32. pylintrc
  33. README.md
  34. 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

Current build status