Meta bug to track issues and actionable items around the performance of frame building. This code runs every frame so performance issues are magnified and even small improvements can accumulate into better power usage. ## Identifying render backend perf issues The primary metric for render backend performance is the `Backend` timings provided by the profiler HUD. The first value is the average over a number of frames which is a good number to look at when the goal is to reduce overall CPU usage and power consumption, while the "max" number is the value to look at when improving janky frame rate. When using the firefox profiler addon, the thread to look at is usually `WRRenderBackend#1` (when a single browser window is open). Make sure to tick the `RenderBackend` box in the profiler's settings before profiling. If getting reliable measurements for a test case is difficult, disabling `gfx.webrender.picture-caching` sometimes help.
Bug 1596042 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Meta bug to track issues and actionable items around the performance of frame building. This code runs every frame so performance issues are magnified and even small improvements can accumulate into better power usage. ## Identifying frame building perf issues The primary metric for frame building performance is the `Backend` timings provided by the profiler HUD. The first value is the average over a number of frames which is a good number to look at when the goal is to reduce overall CPU usage and power consumption, while the "max" number is the value to look at when improving janky frame rates. When using the firefox profiler addon, the thread to look at is usually `WRRenderBackend#1` (when a single browser window is open). Make sure to tick the `RenderBackend` box in the profiler's settings before profiling. If getting reliable measurements for a test case is difficult, disabling `gfx.webrender.picture-caching` sometimes help.
Meta bug to track issues and actionable items around the performance of frame building. This code runs every frame so performance issues are magnified and even small improvements can accumulate into better power usage. ## Identifying frame building perf issues The primary metric for frame building performance is the `Backend` timings provided by the profiler HUD. The first value is the average over a number of frames which is a good number to look at when the goal is to reduce overall CPU usage and power consumption, while the "max" number is the value to look at when improving janky frame rates. When using the firefox profiler addon, the thread to look at is usually `WRRenderBackend#1` (when a single browser window is open). Make sure to tick the `RenderBackend` box in the profiler's settings before profiling. If getting reliable measurements for a test case is difficult, disabling `gfx.webrender.picture-caching` sometimes help. A good target for frame building would be to keep the max timings consistently under 3ms on most pages.