Processes and Threads - Resque vs. Sidekiq
summary
Resque forks a child per job so one worker process handles one active job, parent stays responsive and uses signals for restart and isolation; memory multiplies with processes but leaks get cleaned on exit. Sidekiq uses threads and Celluloid actors with a manager that spins up many processors, a fetcher that pulls work from Redis, and middleware for logging and exponential retries; MRI’s GIL limits CPU-bound thread gains. Choose Resque for strong job isolation and easier safety, Sidekiq for lower memory per worker and higher throughput.
AI-written summary · about
chapters (4)
- 0:00Start
- 19:21THREADS PROS: SHARED MEMORY CONS: SHARED MEMORY
- 21:45ACTORS & CELLULOID
- 31:32SIDEKIQ - HOW?
related talks
39mAsynchronous Workers to the Resque
35mSidekiq at Gusto: The Parts Where People’s Jaw Drops
41mInside ActiveJob
27mFrom Resque to SolidQueue - Rethinking our background jobs for...
28mFair by design: orchestrating background jobs in Ruby
55mThe Past, Present and Future of Background Job...
38mBackground Processing, Serverless Style
20mRecurring Background Jobs with Sidekiq-scheduler