Skip to content

Change scheduler for reactor executor#17842

Merged
srnagar merged 2 commits intoAzure:masterfrom
srnagar:amqp-scheduler
Dec 9, 2020
Merged

Change scheduler for reactor executor#17842
srnagar merged 2 commits intoAzure:masterfrom
srnagar:amqp-scheduler

Conversation

@srnagar
Copy link
Member

@srnagar srnagar commented Nov 27, 2020

This PR is to change the scheduler on which the reactor executor runs. Previously, it was using Scheduler.single() which uses a single thread for the entire process. As more connections are created, all the connections will rely on this single thread to perform service operations which limits the scalability of the number of connections that can be created within a process. The change in this PR is to have a dedicated thread, Schedulers.newSingle(), for each connection which will still keep the underlying proton-j reactor thread-safe while allowing the number of connections to scale.

Fixes #17843
Fixes #17844

@srnagar srnagar self-assigned this Nov 27, 2020
@ghost ghost added the Azure.Core azure-core label Nov 27, 2020
@hemanttanwar
Copy link
Contributor

We should run live test, just to see impact of this change.

@srnagar srnagar requested a review from conniey December 9, 2020 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Azure.Core azure-core

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] EH Clients take long time to instantiate [BUG] Eventhubs throughput doesn't scale with Concurrency

4 participants