This ticket is an alternate attempt to address #57 by using multiple RabbitMQ channels per connection. Since each channel runs in its own goroutine, the processors are also running concurrently. This allows control over the degree of concurrency by specifying a fixed number of channels to use for any given instance, while maintaining a single TCP connection to the server.
The default behavior is to use a single channel, which will give exactly the same result as the current version, Adding --num-channels X at the command line will open multiple channels. As long as the GOMAXPROCS env variable is at least X, this will allow running X concurrent processors handing messages from the queue.
This ticket is an alternate attempt to address #57 by using multiple RabbitMQ channels per connection. Since each channel runs in its own goroutine, the processors are also running concurrently. This allows control over the degree of concurrency by specifying a fixed number of channels to use for any given instance, while maintaining a single TCP connection to the server.
The default behavior is to use a single channel, which will give exactly the same result as the current version, Adding
--num-channels Xat the command line will open multiple channels. As long as the GOMAXPROCS env variable is at least X, this will allow running X concurrent processors handing messages from the queue.