Skip to content

Conversation

@trinity-1686a
Copy link
Contributor

Description

When scheduling leaf splits, allow up to N queries to run concurrently so that a single large query doesn't hog all ressources on a searcher.

How was this PR tested?

added unit test to verify it emits permits in the expected order

pub fn new(num_download_slots: usize, memory_budget: ByteSize) -> Self {
pub fn new(
num_download_slots: usize,
num_concurrent_query: usize,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
num_concurrent_query: usize,
num_concurrent_queries: usize,

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