David Weiser

Currently, we're seeing cases where resque workers are running for 6+ hours and taking 40% of system RAM. Normally, we'd expect (as a very simple rule) that no process will...

+1 on the "after an hour of 90%+ cpu/memory usage, kill." This would be super-similar to how god (http://godrb.com/) does its thing. If you don't want a default of an...

I think that both features would be really useful. The overall problem, IMO, is that sometimes jobs do unexpected things: they use more resources than we wanted then to (which...

I've changed how we implement this in our branch of resque-sliders: https://github.com/seomoz/resque-sliders/commit/c71ac67c84160597fafd30e939346310ff978a5d Basically, we just find all the child processes of the Resque Workers, and if they've been running for...