const Queue = require('bull');
const test = new Queue('test');
test.process('job1', 1, () => { done(); });
test.process('job2', 10, () => { done(); });
Job concurrency of job1 will be 10 per worker, expected 1 per worker.
I think it is not 10 but 11 in this particular case
Am I misunderstanding the process concurrency? For the time being, I've separated the processes to unique queues.
yes, it is not trivial to have different concurrency levels for different named jobs, we may end changing the api so that this behaviour does not come as a surprise.
Okay, thanks for the clarification. I'm okay if this issue is closed.
I can leave it as an enhancement to avoid future duplicates.
i would love to see this improved as well
Also see https://github.com/OptimalBits/bull/blob/master/REFERENCE.md#queueprocess , if you scroll down a bit it's explained there.
@weeco yes - it's explained - but still it should not work like that. and that explanation was added after my issue #719
It is working by design. I don't like this and a few other behaviours either, but since these would be breaking changes I don't see them changing anytime soon.
well may be it could be a seperate feature or tunable behavior- i think some other people can find it usefull as well.
Let's vote :) +1
+1
If it was easy to implement, but the problem is that it requires several important changes in the core, so I do not think it is worth the effort, specially when you can just have 2 different queues to get the desired behaviour.
Except, with multiple queues seems you lose the ability to prioritize and have max concurrency across named jobs.
bump...
I am going to close this, since the issue has become unclear, and there is no proposed solution for it.
What is the maximum amount of concurrency for a process? Anyone know?
@tskweres did you ever find an answer for this?
Most helpful comment
What is the maximum amount of concurrency for a process? Anyone know?