-
Notifications
You must be signed in to change notification settings - Fork 205
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
participant-integration-api: Reuse the services execution context for data munging. #8415
participant-integration-api: Reuse the services execution context for data munging. #8415
Conversation
/azp run |
Pull request contains merge conflicts. |
6b0a7ef
to
09c0408
Compare
In testing on proprietary code, this seems to get about a 5% performance improvement, which I'm putting down to less CPU contention. |
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.
Makes sense. Thank you!
Rather than spawning a separate thread pool for manipulating data before and after index queries, we can just re-use the services EC, which is already a work-stealing thread pool.
CHANGELOG_BEGIN CHANGELOG_END
09c0408
to
cddfea7
Compare
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.
Looks good
This is the obvious follow-up to #7945. We can share the work-stealing execution pool between the indexer and the API server when they run in the same process.
Pull Request Checklist
CHANGELOG_BEGIN
andCHANGELOG_END
tagsNOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with
/AzurePipelines run
totrigger the build.