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: Memory init() #166

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

Performance Audit 2017: Memory init() #166

nicjansma opened this issue Dec 22, 2017 · 3 comments
Labels
fixed-akamai Fixed in the Akamai repo performance

Comments

@nicjansma
Copy link

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
Copy link
Member

if the battery API is being deprecated, we might end up dropping this.
@ashenoy2014
Copy link

ashenoy2014 commented May 8, 2019 •
edited
Loading

PR for this fix has been merged into our private organizational fork and should land in this repository in coming weeks.
@nicjansma nicjansma added the fixed-akamai Fixed in the Akamai repo label May 9, 2019
@ashenoy2014 ashenoy2014 mentioned this issue May 9, 2019
Open
@mc-chaos
Copy link

@nicjansma , if this was Fixed by "Akamai" is this backported with one of the last akamai-backport PRs? Or could this Backported?
regards, Sascha
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed-akamai Fixed in the Akamai repo performance
4 participants
@bluesmoon @nicjansma @ashenoy2014 @mc-chaos