Rename Time To Interactive metrics

To simplify developer messaging, we renamed Time to Consistently
Interactive to just Time to Interactive, and Time to First Interactive
to Time to First CPU Idle. This CL renames variables and functions
appropriately in the time_to_interactive module before we wire them up
to loading_metric.

There are lots of docs lying around that still mention the term "First
Interactive" and "Consistently Interactive", and it will be a while
until we can rename everything appropriately. For the time being, I left
comments in the jsdoc about the previous names of these metrics.

Bug: catapult:#3635
Change-Id: I408aa1cf201a9e4f264697a36a94f9e161dece8c
Reviewed-on: https://chromium-review.googlesource.com/774987
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Reviewed-by: Ben Hayden <benjhayden@chromium.org>
Commit-Queue: Deepanjan Roy <dproy@chromium.org>
2 files changed
tree: bf1c2208e8d3e9fba5a2bbed10c4f4f574bd576d
  1. bin/
  2. catapult_base/
  3. catapult_build/
  4. common/
  5. dashboard/
  6. dependency_manager/
  7. devil/
  8. docs/
  9. experimental/
  10. firefighter/
  11. hooks/
  12. infra/
  13. netlog_viewer/
  14. systrace/
  15. telemetry/
  16. third_party/
  17. trace_processor/
  18. tracing/
  19. web_page_replay_go/
  20. .eslintignore
  21. .eslintrc
  22. .gitignore
  23. AUTHORS
  24. codereview.settings
  25. CONTRIBUTING.md
  26. LICENSE
  27. navbar.md
  28. OWNERS
  29. PRESUBMIT.py
  30. pylintrc
  31. README.md
  32. 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