Skip to content

Conversation

sbosell
Copy link
Contributor

@sbosell sbosell commented Apr 27, 2018

Without being able to modify the prefetch and max concurrent calls the Service Bus clients can not be optimized. I added one setting for the MqServer in addition to the connection string to set the prefetch counts as well as the code to handle the number of threads on the RegisterHanders. Updated documentation/readme.

sbosell added 3 commits April 26, 2018 16:42
Sanitize QueueNames instead of removing MqPrefix
…aults to 0 the azure default)

RegisterHandler allows the number of threads to be set and modifies the OnMessage's MaxConcurrentCalls
Update README.md to reflect these changes
@mythz
Copy link
Member

mythz commented Apr 29, 2018

Can you confirm that this doesn't break existing Service Bus tests? you can change it to use your Azure Service Bus by populating the AZURE_BUS_CONNECTION_STRING environment variable with the connection string to your Azure Service Bus instance.

Although ideally every PR should include a test that tests the feature it adds.

@sbosell
Copy link
Contributor Author

sbosell commented Apr 30, 2018 via email

@sbosell
Copy link
Contributor Author

sbosell commented Oct 6, 2018

I'm coming back to this after a break. @mythz Do you have some suggestions on how to test this besides the existing tests? This is a config of the underlying client so it isn't adding or modifying the functionality of the library only providing some configuration options to help better control the underlying throughput options. Quite frankly without being able to modify those values this MQ client is extremely slow at about 100 messages per minute (handling) across 10 threads.

@mythz
Copy link
Member

mythz commented Oct 6, 2018

The commits just shouldn't break existing tests. You'll also need to update to the latest master before sending another PR as this PR now has conflicts.

@DeonHeyns
Copy link
Contributor

DeonHeyns commented Dec 27, 2018

@sbosell, this is a useful feature for some of the work we are doing. Can I help you with this PR in anyway?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants