search for: solutaion

...sly. This job has to wait until the previous job has finished before it may start. BTW The reason jobs may not run simultaniously is that the jobs do extrernal HTTP-requests. Too many external HTTP-requests for one class may occur a too heavy load for the service this class is using. The most easy solutaion is to do just this for every class I need a worker: QUEUE=<class> rake resque:work The problem with this solution is that it consumes a lot of memory. At the moment I have 30 different classes and it is still growing. Another solution is to let several classes share one queue like this: QUEU...