Skip to content

feat: Separate runtimes for taskbroker components#559

Closed
evanh wants to merge 3 commits into
mainfrom
evanh/feat/separate-runtimes
Closed

feat: Separate runtimes for taskbroker components#559
evanh wants to merge 3 commits into
mainfrom
evanh/feat/separate-runtimes

Conversation

@evanh

@evanh evanh commented Feb 19, 2026

Copy link
Copy Markdown
Member

Create a separate tokio runtime for each of the consumer and gRPC server. The maintenance and upkeep threads will continue to use the default runtime. The number of threads allocated to each runtime is specified by a config setting, or the TOKIO_WORKER_THREADS environment variable or defaults to the number of CPUs.

Create a separate tokio runtime for each of the consumer and gRPC server. The maintenance and upkeep
threads will continue to use the default runtime. The number of threads allocated to each runtime is
either specified by the TOKIO_WORKER_THREADS environment variable or defaults to the number of CPUs.
@evanh evanh requested a review from a team as a code owner February 19, 2026 21:07
Comment thread src/main.rs Outdated

@markstory markstory left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm interested to see how this impacts contention on sqlite, or if the connection can be shared across multiple runtimes.

@evanh

evanh commented Feb 20, 2026

Copy link
Copy Markdown
Member Author

I'm interested to see how this impacts contention on sqlite, or if the connection can be shared across multiple runtimes.

I doubt it will have much impact on SQLite, we would still be locked at one process at a time. This change is meant more for the push taskbroker testing, so we can isolate the push threads from the other components.

@evanh

evanh commented Mar 26, 2026

Copy link
Copy Markdown
Member Author

This is outdated now with the push changes

@evanh evanh closed this Mar 26, 2026
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