defunkt/resque — Issue #460: Problems with overhead forking new process on very large database following change in Rails 3.1
Author: CountCulture
Created: 2011-11-23 22:36:56+00:00
State: open

The problem is detailed at https://github.com/rails/rails/issues/3678#issuecomment-2822031 . Basically from (I think) 3.1.1 each new Rails process gets the primary key for each table. For very large tables, on heavily used databases, this can be a considerable overhead. As far as I can tell, this is happening each time the Resque parent forks a new process (not sure why), but that's both making Resque unusable, and killing the db (happy to be told I'm making an error, or am doing something wrong).

Unfortunately I've just moved from DelayedJob to Resque (and from Rails 3.0 to 3.1), and now wondering which I should downgrade.

Any suggestions?

Chris