Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine most efficient rendering mechanism #13

Open
jamesplease opened this issue Dec 23, 2014 · 0 comments
Open

Determine most efficient rendering mechanism #13

jamesplease opened this issue Dec 23, 2014 · 0 comments
Labels

Comments

@jamesplease
Copy link
Owner

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant