-
Notifications
You must be signed in to change notification settings - Fork 11.9k
perf(@angular/ssr): prevent potential stampede in entry-points cache #28506
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
Conversation
hybrist
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to close as "not worth it". I'm just having flashbacks to issues with cache stampedes during bootup, so I'm a bit overly sensitive about it. :)
e2b408e to
4562c95
Compare
alan-agius4
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, one tiny nit.
4562c95 to
03e1d2c
Compare
If multiple concurrent requests hit `getEntryPointExports`, all of them would previously see the cache miss for entry point. With this change, only the first request will and the others can leverage the cache. This can be important when instances are added to a pool under high traffic.
03e1d2c to
436bcf6
Compare
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
If multiple concurrent requests hit
getEntryPointExports, all ofthem would previously see the cache miss for entry point. With this
change, only the first request will and the others can leverage the
cache.
This can be important when instances are added to a pool under high
traffic.
PR Checklist
Please check to confirm your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information