Faster node start with many classic queues v2 #7676
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lhoguin
reviewed
Mar 20, 2023
mkuratczyk
force-pushed
the
faster-queue-index-start
branch
from
1ed7041 to
1df58e5
Compare
lhoguin
previously approved these changes
Mar 20, 2023
mkuratczyk
force-pushed
the
faster-queue-index-start
branch
from
9076b78 to
1df58e5
Compare
This cuts ~10s of node startup time with 100k classic queues v2.
ensure_dir only if the write failed use raw files
mkuratczyk
force-pushed
the
faster-queue-index-start
branch
from
1df58e5 to
9161634
Compare
mergify bot
pushed a commit
that referenced
this pull request
Mar 21, 2023
* Faster all_queue_directory_names/1 * Optimise writing stub files Combined, this reduces node startup time by half with many empty classic queues v2 (cherry picked from commit 4da170f)
michaelklishin
added a commit
that referenced
this pull request
Mar 21, 2023
Faster node start with many classic queues v2 (backport #7676)
mkuratczyk
added a commit
that referenced
this pull request
Mar 23, 2023
Per-vhost DETS file with recovery terms for all queues is a bottleneck when stopping RabbitMQ - all queues try save their state, leading to a very long file server mailbox and very unpredictable time to stop RabbitMQ (on my machine it can vary from 20 seconds to 5 minutes with 100k classic queues). In this PR we can still read the recovery terms from DETS but we only save them in per-queue files. This way each queue can quickly store its state. Under the same condition, my machine can consistently stop RabbitMQ in 15 seconds or so. The tradeoff is a slower startup time: on my machine, it goes up from 29 seconds to 38 seconds, but that's still better than what we had until #7676 was merged a few days ago. More importantly, the total of stop+start is lower and more predictable. This PR also improves shutdown with many classic queues v1. Startup time with 100k CQv1s is so long and unpredictable that it's hard to even tell if this PR affects it (it varies from 4 to 8 minutes for me).
mkuratczyk
added a commit
that referenced
this pull request
Mar 23, 2023
Per-vhost DETS file with recovery terms for all queues is a bottleneck when stopping RabbitMQ - all queues try save their state, leading to a very long file server mailbox and very unpredictable time to stop RabbitMQ (on my machine it can vary from 20 seconds to 5 minutes with 100k classic queues). In this PR we can still read the recovery terms from DETS but we only save them in per-queue files. This way each queue can quickly store its state. Under the same condition, my machine can consistently stop RabbitMQ in 15 seconds or so. The tradeoff is a slower startup time: on my machine, it goes up from 29 seconds to 38 seconds, but that's still better than what we had until #7676 was merged a few days ago. More importantly, the total of stop+start is lower and more predictable. This PR also improves shutdown with many classic queues v1. Startup time with 100k CQv1s is so long and unpredictable that it's hard to even tell if this PR affects it (it varies from 4 to 8 minutes for me). Unfortunately this PR makes startup on MacOS slower (~55s instead of 30s for me), but we don't have to optimise for that. In most cases (with much fewer queues), it won't be noticable anyway.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Faster CQv2 startup.
On my test box, with 100k CQs (with
classic_queue.default_version = 2), on main:import: ~70 seconds
start_app: ~55-65 seconds
With this PR:
import: ~48 seconds
start_app: ~29 seconds