Increase number of concurrent celery workers in production #1583
Conversation
This file contains 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
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.
This corrects an issue on Heroku currently where we are IO bound on Clickhouse. We need to convert the inserts to be async but until then this will free up resources on the worker nodes to tend to the inserts.
Problem:
We are blocked processing events waiting on inserts to complete on ClickHouse.
Temporary Solution:
Increase concurrency of celery workers on worker nodes since worker boxes are not taxed at all on CPU or Memory.
This should buy us time to refactor inserts to be async into Clickhouse.