-
Notifications
You must be signed in to change notification settings - Fork 102
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
Optimize views/grid #5
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Okay, excellent. So, let's assume there's no easy way to optimize the width changes. But we can very easily optimize everything else. Strip all the jQuery calls out of partialRender and renderElement. Don't look up any elements there either; cache your element lookups beforehand, ideally as raw DOM elements or arrays of DOM elements.
(12:18:10 PM) Ryan Grove: In renderElement, if you make only native DOM calls, that should chop a significant chunk off your cost, even if you still touch all those widths.
(12:18:30 PM) Aphyr: Yeah, I think you're right.
(12:18:32 PM) Ryan Grove: In Chrome and FF, you have a very good native querySelectorAll implementation, so jQuery is pretty unnecessary for that.
The text was updated successfully, but these errors were encountered: