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

[FIXED] #4043 #4048

Merged
merged 1 commit into from Apr 14, 2023
Merged

[FIXED] #4043 #4048

merged 1 commit into from Apr 14, 2023

Conversation

derekcollison
Copy link
Member

Improve performance on storing msgs when multiple subjects exists with multiple messages and we have store limits that are being hit.

This will not fix any performance degradation per se when per subject limits are being hit constantly across a vast array of keys. That will be addressed more so in 2.10.

Resolves #4043

Signed-off-by: Derek Collison derek@nats.io

…h multiple messages and we have store limits that are being hit.

Signed-off-by: Derek Collison <derek@nats.io>
@derekcollison derekcollison requested a review from a team as a code owner April 13, 2023 23:34
Copy link
Member

@wallyqs wallyqs left a comment

Choose a reason for hiding this comment

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

LGTM

@derekcollison derekcollison merged commit 3f8fc5c into main Apr 14, 2023
2 checks passed
@derekcollison derekcollison deleted the multisubject-limits-perf branch April 14, 2023 00:31
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.

Extreme JetStream write performance degredation when subject counts are limited
2 participants