Performance Monitoring uses traces to collect data about monitored processes in your app. A trace is a report that contains data captured between two points in time in your app.
For Apple and Android apps, Performance Monitoring automatically collects a trace for each screen in your app called a screen rendering trace. Each screen rendering trace collects the following metrics:
Slow rendering frames — A metric that measures the percentage of frames that were slow to render for a specific screen
Frozen frames — A metric that measures the percentage of frames that were frozen for a specific screen
You can view data from these traces in the Screen rendering subtab of the traces table, which is at the bottom of the Performance dashboard (learn more about using the console later on this page).
Definition of a screen rendering trace
Each screen rendering trace is identified by the name you called the screen in your app. The collected metrics for this trace are Slow rendering frames and Frozen frames.
Starts for every
Activityclass when the app calls
Stops when the app calls
Metrics collected by screen rendering traces
These traces are out-of-the-box traces, so you cannot add custom metrics or custom attributes to them.
Slow rendering frames
This metric is the percentage of frames that were slow to render for a specific screen. Specifically, this metric is the percentage of screen instances during which more than 50% of frames took longer than 16 ms to render.
This metric is the percentage of frames that were frozen for a specific screen. Specifically, this metric is the percentage of screen instances during which more than 0.1% of frames took longer than 700 ms to render.
Track, view, and filter performance data
To view real time performance data, make sure that your app uses a Performance Monitoring SDK version that's compatible with real time data processing. Learn more.
Track key metrics in your dashboard
To learn how your key metrics are trending, add them to your metrics board at the top of the Performance dashboard. You can quickly identify regressions by seeing week-over-week changes or verify that recent changes in your code are improving performance.
To add a metric to your metrics board, go to the Performance dashboard in the Firebase console, then click the Dashboard tab. Click an empty metric card, then select an existing metric to add to your board. Click on a populated metric card for more options, like to replace or remove a metric.
The metrics board shows collected metric data over time, both in graphical form and as a numerical percentage change.
Learn more about using the dashboard.
View traces and their data
To view your traces, go to the Performance dashboard in the Firebase console, scroll down to the traces table, then click the appropriate subtab. The table displays some top metrics for each trace, and you can even sort the list by the percentage change for a specific metric.
If you click a trace name in the traces table, you can then click through various screens to
explore the trace and drill down into metrics of interest. On most pages, you can use the
- Filter by App version to view data about a past release or your latest release
- Filter by Device to learn how older devices handle your app
- Filter by Country to make sure your database location isn't affecting a specific region
Learn more about viewing data for your traces.
Learn more about using attributes to examine performance data.
Learn more about how to track performance issues in the Firebase console.