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

Avoid growing notifications map during recovery #385

Merged
merged 1 commit into from
Jun 28, 2023
Merged

Conversation

kjnilsson
Copy link
Contributor

As this could negatively affect recovery performance of long logs.

Proposed Changes

Please describe the big picture of your changes here to communicate to the
RabbitMQ team why we should accept this pull request. If it fixes a bug or
resolves a feature request, be sure to link to that issue.

A pull request that doesn't explain why the change was made has a much
lower chance of being accepted.

If English isn't your first language, don't worry about it and try to
communicate the problem you are trying to solve to the best of your abilities.
As long as we can understand the intent, it's all good.

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation (correction or otherwise)
  • Cosmetics (whitespace, appearance)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • All tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in related repositories

Further Comments

If this is a relatively large or complex change, kick off the discussion by
explaining why you chose the solution you did and what alternatives you
considered, etc.

As this could negatively affect recovery performance of long logs.
@mkuratczyk
Copy link
Contributor

Nice one! In my test scenario - a quorum queue with 10 million 5kb messages, the recovery process on node startup went down from ~250s to ~170s. On top of that, the memory consumption during recovery went down as well as expected.

Here's the memory usage during the node startup (with just that one queue), first with this PR, then with main:
Screenshot 2023-06-27 at 15 32 04

@kjnilsson kjnilsson marked this pull request as ready for review June 28, 2023 08:11
@kjnilsson kjnilsson merged commit 9be1971 into main Jun 28, 2023
7 checks passed
mkuratczyk added a commit to rabbitmq/rabbitmq-server that referenced this pull request Jul 13, 2023
Improved long log recovery:
faster and lower memory usage.

more info:
rabbitmq/ra#385
@michaelklishin michaelklishin added this to the 2.6.3 milestone Jul 13, 2023
@michaelklishin michaelklishin deleted the recover-opt branch July 13, 2023 15:30
mergify bot pushed a commit to rabbitmq/rabbitmq-server that referenced this pull request Jul 13, 2023
Improved long log recovery:
faster and lower memory usage.

more info:
rabbitmq/ra#385

(cherry picked from commit 805f679)
mergify bot pushed a commit to rabbitmq/rabbitmq-server that referenced this pull request Jul 13, 2023
Improved long log recovery:
faster and lower memory usage.

more info:
rabbitmq/ra#385

(cherry picked from commit 805f679)
(cherry picked from commit 2c21b65)
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.

None yet

3 participants