Skip to content

Run Puma in single mode on Render free tier #22

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.

Sign up for GitHub

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

Merged
raghubetina merged 1 commit into from
May 18, 2026
Merged

Run Puma in single mode on Render free tier #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion render.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,12 @@ services:
sync: false
# Memory optimization for Render free tier (512MB RAM)
- key: WEB_CONCURRENCY
value: "1" # Single worker to fit in 512MB
# 0 = Puma single mode (the master process serves HTTP directly,
# no forked workers). Any value ≥ 1 spawns that many worker
# processes on top of the master, each adding ~150MB. Combined
# with the four Solid Queue subprocesses below, anything above
# single mode OOMs on the 512MB free tier.
value: "0"
- key: RAILS_MAX_THREADS
value: "3" # Cap threads to reduce memory
- key: MALLOC_ARENA_MAX
Expand Down