Skip to content

Conversation

@joshleblanc
Copy link
Contributor

This is less of a "this is ready to be merged", and more of an effort to reinvigorate conversation around this feature. I cobbled this together as a proof of concept because I simply couldn't use the multi-process approach on the server I'm trying to deploy to. This is related to #343, and tries to naively reimplement this

I originally stumbled on this feature because I was testing Kamal on a 1GB VPS. The initial deploy would work, however there wasn't enough resource headroom for the second deploy. I narrowed this down to SQ using ~100MB per process, essentially taking up half the available memory on the system.

image

After implementing this change, I saw the application memory drop from ~700MB to ~270MB.

image

The usage is simply placing this in puma.rb

if ENV["SOLID_QUEUE_IN_PUMA"]
  plugin :solid_queue
  solid_queue_mode :async
end

I currently have this deployed to a 1GB droplet - the application is running quickly, background jobs are running, and redeploys are succeeding

@ka8725
Copy link

ka8725 commented Oct 11, 2025

@joshleblanc thanks for this amazing job! I installed the fork in an app hosted on Heroku that servers webhooks from a live application. I've run it as a separate process though (as a worker). My Procfile:

web: bin/rails server -p $PORT -e $RAILS_ENV
worker: bin/jobs --mode=async

So far it looks very good:

image

I used to run the worker before without recurring jobs because it would consume all RAM. Now, even with recurring jobs it takes ~2x less RAM! Thanks for sharing this work!

@rosa rosa mentioned this pull request Nov 5, 2025
@headius
Copy link

headius commented Nov 5, 2025

I'd like to help get this finished up, so that non-forking implementations like JRuby can use Solid Queue. Is it complete enough that I could try to run on JRuby now and see what's missing? Do you have an example I could try?

@headius
Copy link

headius commented Nov 5, 2025

See #679 for my recent request to have a non-forking implementation.

@CufeHaco
Copy link

CufeHaco commented Nov 5, 2025

Just give me a bit.more time on the JEP-380 socket PR. I can talk to Cruby, C, or any other language using jruby as the layer via Linux Sockets.

Separation of concerns. Let both interpreters run as independent processes and communicate via unix sockets and message pack.

I should having it ready by this evening/tomorrow morning.

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.

4 participants