Improve performance of query endpoint and ZAAS client #805
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jandadav
changed the title
this fixes a cache miss Signed-off-by: jandadav <janda.david@gmail.com>
Signed-off-by: jandadav <janda.david@gmail.com>
jandadav
force-pushed
the
rip/dj/auth-performance-evaluation
branch
from
8315ed0 to
0253517
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
taban03
reviewed
Aug 27, 2020
zaas-client/src/main/java/org/zowe/apiml/zaasclient/service/internal/HttpsClientProvider.java
Show resolved
Hide resolved
taban03
approved these changes
Aug 27, 2020
delete-merged-branch
bot
deleted the
rip/dj/auth-performance-evaluation
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Improve performance of query endpoint and ZAAS client
The ZAAS client had query performance measured on SDK sample including ZAAS client around 700ms. With heavy load, we measured a performance degradation up to 10x (7s per request)
After the fix, with heavy load, the requests take around 300ms and do not scale with load
Type of change
Please delete options that are not relevant.