Avoid duplicated generation of APISpecification objects #3940
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
What was the end-user or developer problem that led to this PR?
gem install aws-sdk
is painfully slowWhat is your fix for the problem, implemented in this PR?
As far as I could see,
Gem::Resolver::APISpecification
objects aresupposed to be immutable. If my guessing is correct, then we can cache
and reuse its instances for performance.
At least,
rake
passes on my machine.Before this change:
After this change:
Tasks:
I will abide by the code of conduct.