You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, WebRender traverses full display lists of a page in the scene builder thread, even when only a portion of the display lists have changed. This results in suboptimal performance for the scene builder thread. A similar issue was raised five years ago (#4046 ). Are there any better feasible solutions available now?
The text was updated successfully, but these errors were encountered:
Unfortunately no. It's pretty high in the list of issues but it is a very large undertaking and we haven't managed to dedicate the necessary resources to do it.
Unfortunately no. It's pretty high in the list of issues but it is a very large undertaking and we haven't managed to dedicate the necessary resources to do it.
Can I ask why does Servo build the property tree in WebRender after receiving the full display list, rather than completing the property tree creation during the display list creation? What was the original reason for this design?
Currently, WebRender traverses full display lists of a page in the scene builder thread, even when only a portion of the display lists have changed. This results in suboptimal performance for the scene builder thread. A similar issue was raised five years ago (#4046 ). Are there any better feasible solutions available now?
The text was updated successfully, but these errors were encountered: