Jobs on RabbitMQ queues are limited to only one executing job at a time per queue for each server

[mthierba]

Queue consumers - one of which is created for each Hangfire queue - are configured with a prefetchCount setting of '1':

Hangfire.SqlServer.RabbitMq/src/Hangfire.SqlServer.RabbitMq/RabbitMqJobQueue.cs

Line 111 in e72d8ee

_channel.BasicQos(0, 1, false);

The result of that is that each consumer will only be allowed to have one message (job) unacked - which they are whilst being processed. Even if more workers are configured and available on a given server, they are all made to wait for one job to be completed until another one can be started.

[mthierba]

It should be noted that #3 does not change the behavior described above automatically as current consumers of the library might explicitly or implicitly depend on it, and it would be a breaking change requiring a major version bump.

What it does it to introduce an extra configuration setting PrefetchCount which users are highly encouraged to leverage, however:

sqlServerStorage.UseRabbitMq(rabbit =>
{
    rabbit.HostName = "localhost";
    rabbit.PrefetchCount = 10;
}, "default", "critical");

^ This allows up to 10 jobs to be executed in parallel for each queue and server.