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.

Sign up for GitHub

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

Jump to bottom

Optimize the named property tracker by not walking the entire tree #1174

Merged
merged 2 commits into from
Jul 26, 2015
Merged

Optimize the named property tracker by not walking the entire tree #1174

merged 2 commits into from
Jul 26, 2015

Commits on Jul 26, 2015

  1. A benchmark for a performance issue when removing a named property

    @Joris-van-der-Wel
    Joris-van-der-Wel committed Jul 26, 2015
    Configuration menu
    Copy the full SHA
    457ff9c View commit details
    Browse the repository at this point in the history

  2. Optimize the named property tracker by not walking the entire tree 

    Testing if a named property can be untracked is now many times faster, which means `setAttribute()` and `removeChild()` will not be slowed by it.
Looking up a named property will also be faster for huge documents
    @Joris-van-der-Wel
    Joris-van-der-Wel committed Jul 26, 2015
    Configuration menu
    Copy the full SHA
    bcf0533 View commit details
    Browse the repository at this point in the history