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
I noticed decreased performance while opening (big) fragments in designer since this PR: #6393. The problem occurs on google chrome browser and takes ~6 seconds to open fragment with ~30 nodes. The same fragment is opened on firefox with 0.5sec or even less. I analyzed this using Chrome's profiler and this is caused by using costly CSS selector introduced in mentioned PR:
💥 Proposal
I noticed decreased performance while opening (big) fragments in designer since this PR: #6393. The problem occurs on google chrome browser and takes ~6 seconds to open fragment with ~30 nodes. The same fragment is opened on firefox with 0.5sec or even less. I analyzed this using Chrome's profiler and this is caused by using costly CSS selector introduced in mentioned PR:
I propose to exchange it with sth cheaper.
This Chrome's behavior is probably caused by the fact it uses single-threaded engine for computing layouts.
The text was updated successfully, but these errors were encountered: