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

Performance Audit 2017: Memory init() #166

Open
nicjansma opened this Issue Dec 22, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@nicjansma

nicjansma commented Dec 22, 2017

The Memory plugin's init() frequently shows up in JavaScript CPU profiles. While it doesn't take a long time, we can often see a few ms of activity.

image

It appears the call to navigator.getBattery() might be expensive. We should investigate if we can defer this work until the beacon (off the critical path).

@bluesmoon

This comment has been minimized.

Show comment
Hide comment
@bluesmoon

bluesmoon Dec 22, 2017

if the battery API is being deprecated, we might end up dropping this.

bluesmoon commented Dec 22, 2017

if the battery API is being deprecated, we might end up dropping this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment