安卓系统上Airbnb的页面性能得分

Part 4 of our series on Airbnb’s Page Performance Score.

Airbnb’s home grown Page Performance Score (PPS) is designed to capture the rich, complex realities of performance by collecting a multitude of user-centric performance metrics and formulating them into one single 0-100 score. In this post we will deep dive into how we define and implement these metrics on Android. Make sure you read the overview blog post first to familiarize yourself with our PPS metrics and formula.

Airbnb自创的页面性能评分（PPS）旨在通过收集大量以用户为中心的性能指标，并将其制定为一个单一的0-100分，来捕捉丰富而复杂的性能现实。在这篇文章中，我们将深入探讨我们如何在Android上定义和实现这些指标。请确保你先阅读概述博文以熟悉我们的PPS指标和公式。

Instrumentation

仪器仪表

The entire customer journey on Airbnb is divided into different pages, each of which has its own measured PPS. In order to support this page-based performance tracking system, we built a standardized infrastructure that enables engineers to configure pages representing their features.

Airbnb的整个客户旅程被划分为不同的页面，每个页面都有自己的测量PPS。为了支持这种基于页面的性能跟踪系统，我们建立了一个标准化的基础设施，使工程师能够配置代表其功能的页面。

On Android a page is associated with a Fragment. Each fragment must provide a LoggingConfig object specifying a page name, which can later be retrieved whenever the page name needs to be referenced. We collect performance data throughout the fragment’s lifecycle, and only emit the logging event when the fragment is paused.

在Android上，一个页面与一个片段相关联。每个片段都必须提供一个指定页面名称的LoggingConfig对象，以后只要需要引用页面名称，就可以检索到该对象。我们在片段的整个生命周期中收集性能数据，并且只在片段暂停时发出日志事件。

A universal PageName enum is used to uniquely identify each page, and is referenced across all platforms to consistently represent each page in our user journey.

一个通用的PageName枚举被用来唯一地识别每个页面，并在所有平台上被引用，以一致地代表我们用户旅程中的每个页面。

Capturing Wait Time Perceived by Users

捕捉用户感知的等待时间

A key differentiator of our new Page Performance Score (PPS) is that it measures wait time that users can see. While our early measurement effort (mentioned in our overview blog post), which was based on the commonly known Time To Interactive (TTI) metric, measures code execution t...