Skip to content

FAQGuidesChangelogShow & Tell

Loading…

Rails 8 solid_queue on Larkhost: one pod or two?

Rails rails processes

tomaszbRegularyesterday

88 views · 0 likes · 2 users

gilbertwyesterday

We ran it in Puma for a small app without problems. Once jobs got heavy we split it out so a slow job could not starve web requests.

Related topics

Pod stuck in "starting" for 15 hours after resume1 reply
Unable to authorize access: must authenticate with the git host1 reply
Node.js app memory climbs until OOM — only on Larkhost2 replies
Pod restarts by itself 1–3 minutes after waking from idle1 reply
Laravel queues stop processing after a deploy1 reply
How is burrow RAM billed? Does it include the page cache?1 reply

Suggested topics

Deploying a Django app with background workers: what is the cleanest setup?2 replies
The back porch: what are you running on a single shared-cpu pod?3 replies
Python 3.13 images are now the default for new launches2 replies
Node.js app memory climbs until OOM — only on Larkhost2 replies
Laravel queues stop processing after a deploy1 reply

With solid_queue living in the same database, is it fine to run the queue inside the web process via the Puma plugin, or does it need its own pod?