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 thought that reducing the # of DOM operations affecting attached nodes would provide a huge speed boost, but Minionette does not do this, and preliminary tests show that my method may, in fact, be slower. Ref
Todo: learn more about reflows and browser performance. What causes a reflow? Why aren't those 10k DOM operations slowing anything down?
When Marionette switched to a document fragment to buffer its collection view rendering, it apparently got a big speed boost. What was the reason behind that? Is it not the same principle here?
Lots of articles on reflow mention that adding/removing nodes will always cause a reflow. And these operations are doing precisely that...so I should do more research on what's happening!
The text was updated successfully, but these errors were encountered:
I thought that reducing the # of DOM operations affecting attached nodes would provide a huge speed boost, but Minionette does not do this, and preliminary tests show that my method may, in fact, be slower. Ref
Todo: learn more about reflows and browser performance. What causes a reflow? Why aren't those 10k DOM operations slowing anything down?
When Marionette switched to a document fragment to buffer its collection view rendering, it apparently got a big speed boost. What was the reason behind that? Is it not the same principle here?
Lots of articles on reflow mention that adding/removing nodes will always cause a reflow. And these operations are doing precisely that...so I should do more research on what's happening!
The text was updated successfully, but these errors were encountered: