4 ms·
i'm not sure why i should use this instead of delayed job for instance
by dorianmariefr 6y ago
i'm not sure why i should use this instead of delayed job for instance
- pqdbr 6y agoIf you're using delayedjob, I strongly suggest you check out the Performance table in Sidekiq's readme. 465 seconds for DelayedJob against 14 seconds for Sidekiq for the same workload. It's 7100 jobs/sec x 215 jobs/sec. I wonder how GoodJob will compare. https://github.com/mperham/sidekiq#performance https://github.com/mperham/sidekiq#performance
- mbell 6y agoThat benchmark is just showing job overhead. That Sidekiq can do nothing 7100 times a second only matters when overhead is significant, i.e. when your jobs do almost nothing.
- thibaut_barrere 6y agodelayed_job hasn't seen a release in 1 year, if that matters to you https://rubygems.org/gems/delayed_job/ https://rubygems.org/gems/delayed_job/