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

Investigate Forced Dispatch performance for providers #429

Open
to11mtm opened this issue Aug 2, 2024 · 0 comments
Open

Investigate Forced Dispatch performance for providers #429

to11mtm opened this issue Aug 2, 2024 · 0 comments
Assignees

Comments

@to11mtm
Copy link
Member

to11mtm commented Aug 2, 2024

An interesting thing to remember about the way .SelectAsync() works as a stage, is that it will only yield if the method is actually async.

In other words, if a DB Call is fully synchronous (i.e. SQLite) there may be minimal benefit to parallelism settings as well as a potential loss in overall throughput.

Looking into whether wrapping the main write/read loop logic in a Task.Run and comparing benchmarks, will at least give a baseline idea of whether to make a change (e.x. adding a config switch).

If not we can document here in case it comes up again :)

@to11mtm to11mtm self-assigned this Aug 2, 2024
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

No branches or pull requests

1 participant