Skip to content
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

feat(kafka): use a thread pool executor for kafka for thread reuse #5079

Merged

Conversation

RyanHolstien
Copy link
Collaborator

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@github-actions
Copy link

github-actions bot commented Jun 3, 2022

Unit Test Results (build & test)

334 tests  +1   334 ✔️ +1   3m 4s ⏱️ +17s
  78 suites +1       0 💤 ±0 
  78 files   +1       0 ±0 

Results for commit 0a7125a. ± Comparison against base commit b2d957d.

♻️ This comment has been updated with latest results.

import org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor;


public class ThreadPoolContainerCustomizer
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this have any processing throughput implications in the default case?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's possible, it might make sense to performance test this before pushing it through. Logically it shouldn't, it's essentially doing the same thing as before just with thread reuse.

@jjoyce0510 jjoyce0510 merged commit e06df1f into datahub-project:master Jun 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants