-
Notifications
You must be signed in to change notification settings - Fork 616
fix(util-user-agent-node): should memoize app id #2223
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
Co-authored-by: Tyson Andre <[email protected]>
8b52d34
to
db3f5c3
Compare
Not a maintainer, but LGTM. nit - in case of future refactorings reintroducing similar bugs or sharing the same array object it might still be useful to assert the length is the expected value |
Codecov Report
@@ Coverage Diff @@
## main #2223 +/- ##
=======================================
Coverage ? 61.83%
=======================================
Files ? 454
Lines ? 23290
Branches ? 5521
=======================================
Hits ? 14402
Misses ? 8888
Partials ? 0 Continue to review full report at Codecov.
|
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
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.
Not a maintainer, but don't see any other issues
Thanks @TysonAndre for looking into this PR. 👍 |
Great! Thank you for fixing this. When do you plan to release? I would like to retry our perf test with this fix in place. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Issue
Resolves: #2027
Description
This change fix an issue that SDK need to read shared config files to load App ID for every request. Now this change only load the App ID once at the client instantiation. This will remove some performance overhead.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.