Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move producers polling into a single thread #298

Open
mensfeld opened this issue Oct 13, 2023 · 0 comments
Open

Move producers polling into a single thread #298

mensfeld opened this issue Oct 13, 2023 · 0 comments
Assignees

Comments

@mensfeld
Copy link
Member

With #56 and #119 there will be much bigger need for one producer per thread.

This cannot be done in an efficient way if we create a thread per instance hence this proposal.

In order to make sure we do not change the behaviour for multi-threaded single producer and we ensure the consistent experience of deliveries as we do now the proposition is as follows:

  1. Create a single thread for all producers
  2. Look into fiber scheduler to be able to wake up in an async manner OR investigate some sort of improvements over current polling mechanism and the CPU usage of a 1ms polling (dunno yet)

The current threading model is def. not sufficient for multi-threaded operations and due to the producer "self managing" polling it seems this needs to be done at this layer

@mensfeld mensfeld self-assigned this Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant