-
Notifications
You must be signed in to change notification settings - Fork 47.2k
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
Improve DEV performance in Chrome #7483
Conversation
Kinda weird. Is Uglifyjs used for building or some another tool? |
Sounds good to me. Agree it's weird that prod mode is no faster. |
@gaearon Do you think it really makes sense? Actually, folks always use prod version in the wild. |
Yes, I uglified during the tests.
As I said earlier this doesn’t have any downsides in production so I’m not sure what you are worried about. I’m saying it “makes sense” because both these fields are numbers anyway so |
That's point! Agreed. |
* Ensure this._domID is always a number * Ensure this._rootNodeID is always a number (cherry picked from commit 4b734f7)
This consistently improves DEV performance in Chrome.
Before this change:
After this change:
This only seems to help DEV in Chrome. I did not observe any significant difference in PROD in Chrome, or in either build in Firefox or Safari.
Normally it would be too much dogscience but I feel the wins for Chrome DEV (most common use case) are significant, they are consistently reproducible, and it kinda makes sense to use numbers anyway.