# Entry to Performance Debugging Tools

# showPerformanceOverlay

Displays usage of raster thread and ui (render) thread, thread busy is shown in red

Raster thread: If you find it time-consuming, it may be too complicated to draw the content, such as a lot of backdrop-filter, overflow: hidden, opacity These properties have an impact on the time consumed by rasterization and can be suggested to reduce the use of these properties. You can also add a will-change: contents wxss attribute to frequently updated nodes to avoid extensive repainting (but this attribute should also be avoided using too much, which would be counterproductive).
UI thread: Generally, it depends on whether type = "list" is not used. If it is useless, layout and paint will be time-consuming.
Thread-related references

Display a board grid on the screen. The components that display the board grid are supposed to be cached

If you find a change in the color of the board grid, this component is re-rendered
If you scroll and the element is still in the screen, the color has been changing, then there is a problem, that there is no cache, this time will affect the scrolling performance.In this case, list-view (type = list) may not work, or you can use will-change: contents to manually add a draw boundary
Not all components will form a RasterCache, it needs to be more complex to