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

lower contention on AggregationLimits #2394

Merged
merged 1 commit into from
May 15, 2024
Merged

lower contention on AggregationLimits #2394

merged 1 commit into from
May 15, 2024

Conversation

PSeitz
Copy link
Contributor

@PSeitz PSeitz commented May 10, 2024

PR quickwit-oss/quickwit#4962 fixes an issue
where the AggregationLimits are not passed correctly. Since the
AggregationLimits are shared properly we run into contention issues.

This PR includes some straightforward improvement to reduce contention,
by only updating if the memory changed and avoiding the second read.

We probably need some sharding with multiple counters or local caching before updating the
global after some threshold.

PR quickwit-oss/quickwit#4962 fixes an issue
where the AggregationLimits are not passed correctly. Since the
AggregationLimits are shared properly we run into contention issues.

This PR includes some straightforward improvement to reduce contention,
by only calling if the memory changed and avoiding the second read.

We probably need some sharding with multiple counters or local caching before updating the
global after some threshold.
@PSeitz PSeitz requested a review from fulmicoton May 10, 2024 10:56
@PSeitz PSeitz merged commit 5b7cca1 into main May 15, 2024
4 checks passed
@PSeitz PSeitz deleted the agg_limits branch May 15, 2024 10:25
philippemnoel pushed a commit to paradedb/tantivy that referenced this pull request Aug 31, 2024
PR quickwit-oss/quickwit#4962 fixes an issue
where the AggregationLimits are not passed correctly. Since the
AggregationLimits are shared properly we run into contention issues.

This PR includes some straightforward improvement to reduce contention,
by only calling if the memory changed and avoiding the second read.

We probably need some sharding with multiple counters or local caching before updating the
global after some threshold.
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.

2 participants