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.

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 performance of HSTS module #270

Open
designfrontier opened this issue Oct 7, 2016 · 5 comments
Open

Improve performance of HSTS module #270

designfrontier opened this issue Oct 7, 2016 · 5 comments

Comments

@designfrontier
Copy link
Member

Line 13 of security/hsts.js throws a Not Optimized: Inlining bailed out warning when you are profiling monument apps. Also points to line 33 in the same file. Need to get this function to inline nicely for better performance.

https://www.dropbox.com/s/vru0q99afk9tqae/Screenshot%202016-10-06%2021.28.15.png?dl=0

@designfrontier
Copy link
Member Author

See also: GoogleChrome/devtools-docs#53

@shibanovp
Copy link
Contributor

shibanovp commented Oct 14, 2016

Hi @designfrontier
Please provide more info about the environment because measuring performance is a tough task.

  1. OS?
  2. Node version
  3. How do you debug it? --inspect flag + chrome unstable / chrome canary?

When I tried to reproduce the issue there was no warning.

@designfrontier
Copy link
Member Author

node version 6.7
Running on OS X
--inspect flag plus public chrome

The performance warning itself is tied to GoogleChrome/devtools-docs#53 (comment) and has to do with hidden classes.

I'll check and see if this is reproducible on 6.8 this morning

@shibanovp
Copy link
Contributor

shibanovp commented Oct 14, 2016

Tested on
screenshot from 2016-10-14 20-47-43
Seems that hsts gets optimized. Even with 6.3.0 it is ok.
screenshot from 2016-10-14 20-45-23

Maybe this issue specific to some settings? I tried includeSubDomains true and false.

@designfrontier
Copy link
Member Author

I haven't had a chance to dig into this over the weekend... hopefully tonight. It's possible it was something in my env.

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

No branches or pull requests

2 participants