Hacker News new | past | comments | ask | show | jobs | submit login

i'm not sure why i should use this instead of delayed job for instance



If 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


That 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.


delayed_job hasn't seen a release in 1 year, if that matters to you https://rubygems.org/gems/delayed_job/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: