Limit app to a single CPU and Solid Queue to 1 thread/1 process - #101
Merged
Conversation
Cap the Kamal web container at one CPU core via `options: { cpus: 1 }`
(renders to `docker run --cpus 1`) and pin Puma to a single worker with
WEB_CONCURRENCY=1. Pin the in-Puma Solid Queue worker to 1 thread and 1
process in config/queue.yml.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or 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
1 participant
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.
Caps the Kamal
webcontainer at one CPU core viaoptions: { cpus: 1 }(renders todocker run --cpus 1) and pins Puma to a single worker withWEB_CONCURRENCY=1. Pins the in-Puma Solid Queue worker to 1 thread and 1 process inconfig/queue.yml(hardcoded so it can't be bumped viaJOB_CONCURRENCY). These are deploy-time config changes that take effect on the nextbin/kamal deploy.🤖 Generated with Claude Code