Consider making ConsumerDispatchConcurrency a per-consumer setting instead of a per-connection setting #1348
Description
Is your feature request related to a problem? Please describe.
Currently if we want concurrent processing we need to set ConsumerDispatchConcurrency on the connection to > 1 (preferably in an AsyncBasicConsumer). This value can be tuned together with the Prefetch count to achieve desired throughput.
If your program contains multiple consumers and you want to have each configured with a different throughout then ConsumerDispatchConcurrency should (in theory) be set to the max of what is needed on each individual consumer as it is a global on the connection. There can also be combinations that are not possible without using a separate connection per consumer.
Describe the solution you'd like
Have ConsumerDispatchConcurrency be a setting on the Consumer instead of on the Connection.
Describe alternatives you've considered
No response
Additional context
Please let me know if I am missing some knowledge related to usage, such that it is preferred to use multiple connections per program to isolate consumers.