Selwin Ong

Yes, that’s the general idea. I thought about making a method that returns the callable to run the worker but I think returning the actual process would give more flexibility.On...

@jackkinsella I released RQ 1.16.1 with `worker_pool.get_worker_process()`. It would be great if someone can create a PR implementing this in django-RQ.

I'm open to this, but before this is implemented, I'd also want RQ to be able to keep a history of results from job executions.

Another alternative is to introduce a memcached backed engine similar to `django.contrib.sessions.backends.cached_db`. While it doesn't necessarily reduce query counts, it will at least take the load off your main DB....

> Concurrency has been a big topic for quite a while now. At the moment both the SimpleWorker and the Worker are very mature, but to be honest, it's going...

> So this would be a bit more similar to what Celery does in which you have a single worker, and you just pass the --concurrency num and the --pool...

> Doesn’t WorkerPool implementation, being a layer of abstraction on top of the worker reduces the flexibility for custom classes, since it hides details that one would want to customize...

I haven't had the time to look at this PR closely, for a PR this ambitious, I think we'll need time to iterate. If you think there's a few chunks...

Yes, I'd like to take a more in depth look when I have more time. Thanks for getting this PR this far, expect more changes as we get this into...

I need to think further to further group some sections inside `work()` so that you don't need to rewrite so much of it. On a more meta perspective, since we...