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

Performance Audit 2017: Beacon: Memory: Node counting is expensive #176

Open
nicjansma opened this issue Dec 22, 2017 · 0 comments
Open

Performance Audit 2017: Beacon: Memory: Node counting is expensive #176

nicjansma opened this issue Dec 22, 2017 · 0 comments
Labels
performance

Comments

@nicjansma
Copy link

The Memory plugin looks at the DOM to get node counts of various types of nodes. This query does show up in CPU profiling:

image

We should look into whether this cost can be reduced.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
performance
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nicjansma