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

Support configurable parallelism #31

Merged
merged 5 commits into from
Sep 16, 2024

Conversation

fpacifici
Copy link
Contributor

Producing large requests (like Clickhouse batches) takes time.
Running the worker in Kubernetes implies having a set number
of cores available.

This introduces the need to be able to configure the maximum
number of threads used to produce requests to have requests
ready when needed.

The longer it takes to build request the higher the parallelism.
The lower the number of cores the lower the parallelism in
order not to be throttled.

This also fixes the push-image script not to have the
artifact registry hardcoded.

produce the requests for the target. This allows us to have a request ready as
soon as it is needed even when high volume is needed.

It is important to set this parameter accurately specifically when the worker
Copy link
Member

Choose a reason for hiding this comment

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

I personally wouldn't know how to set this number accurately

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added some hints

@fpacifici fpacifici merged commit b2d6ecd into master Sep 16, 2024
2 checks passed
@fpacifici fpacifici deleted the fpacifici/parameter_for_parallelism branch September 16, 2024 21:56
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