DEV Community

Discussion on: Switching From Resque to Sidekiq

rudolfolah profile image
Rudolf Olah

Going to investigate further but that sounds about right. I had to switch something from an async Resque job to a synchronous long-running process running while SSH'd into an instance.

And this article from 2015 seems to also confirm the dirty exits issue:

TL;DR: Reduce the number of workers. Make smaller jobs.
I went from a 50% failure rate, to zero

It seems like the common failure rate for Resque is between 3% and 10% with some outliers of 0% or 1% or in this crazy case, 50%. I guess how acceptable this is depends on how much engineering talent you can spend on patching these issues.