Adding support for using multiple RabbitMQ channels per connection #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.