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

Concurrency in Assigner should be restricted for memory only operations. Disk IO in Assigner should be submitted via a dedicated IO ExecutionContext #341

Open
simerplaha opened this issue Dec 11, 2021 · 0 comments

Comments

@simerplaha
Copy link
Owner

simerplaha commented Dec 11, 2021

Compaction can be configured to be highly concurrent for all in-memory operations which also means that it is also concurrent sometimes for initialising Segment iterators (Disk IO) which should be sequential and not concurrent and submitted via dedicated IO ExecutionContext.

This is related to #330.

@simerplaha simerplaha changed the title Concurrency in Assigner should be restricted for CPU & RAM bound operations only. Disk IO in Assigner should be submitted to dedicated IO ExecutionContext Concurrency in Assigner should be restricted for CPU & RAM bound operations only. Disk IO in Assigner should be submitted via a dedicated IO ExecutionContext Dec 11, 2021
@simerplaha simerplaha changed the title Concurrency in Assigner should be restricted for CPU & RAM bound operations only. Disk IO in Assigner should be submitted via a dedicated IO ExecutionContext Concurrency in Assigner should be restricted for memory only operations. Disk IO in Assigner should be submitted via a dedicated IO ExecutionContext Dec 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant