The Telemetry loading benchmark measure Chrome's loading performance under different network and caching conditions.
There is currently one loading benchmarks:
loading.cluster_telemetry: A cluster Telemetry benchmark that uses the corpus of top 10 thousands URLs from Alexa. This benchmark is triggered on-demand only.If you're just trying to gauge whether your change has caused a loading regression, you can run the loading benchmark through the Cluster Telemetry service. You can specify a Gerrit patch for them and compare the results with and without the patch applied.
You can run loading.cluster_telemetry (top 10k pages) through Cluster Telemetry service (Cluster Telemetry is for Googler only).
The loading test cases are divided into groups based on their network traffic settings and cache conditions.
All available traffic settings can be found in traffic_setting.py
All available caching conditions can be found in cache_temperature.py
The benchmark output several different loading metrics. The keys one are:
Besides those key metrics, there are also breakdown metrics that are meant to to make debugging regressions simpler. These metrics are updated often, for most up to date information, you can email speed-metrics-dev@chromium.org or chrome-speed-metrics@google.com (Googlers only).