From 03bfe0a4467b89d2b356e5ce4031785e908876cb Mon Sep 17 00:00:00 2001 From: Michael Klishin Date: Mon, 20 Mar 2023 08:37:26 +0400 Subject: Make CQv2 the new default CQv2 is significantly more efficient (x2-4 on some workloads), has lower and more predictable memory footprint, and eliminates the need to make classic queues lazy to achieve that predictability. Per several discussions with the team. --- release-notes/3.12.0.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) (limited to 'release-notes') diff --git a/release-notes/3.12.0.md b/release-notes/3.12.0.md index 69eb6f2b08..418610d021 100644 --- a/release-notes/3.12.0.md +++ b/release-notes/3.12.0.md @@ -109,9 +109,17 @@ in the `3.11.x` release series. GitHub issue: [#7553](https://github.com/rabbitmq/rabbitmq-server/pull/7553#issuecomment-1463660454) - * Reduced memory footprint, improved memory use predictability and throughput of classic queues. + * Reduced memory footprint, improved memory use predictability and throughput of classic queues (version 2, or CQv2). This particularly benefits classic queues with longer backlogs. + Classic queue v2 (CQv2) storage implementation **is now the default**. It is possible to switch + the default back to CQv1 using `rabbitmq.conf`: + + ``` ini + # uses CQv1 by default + classic_queue.default_version = 1 + ``` + GitHub issues: [#4522](https://github.com/rabbitmq/rabbitmq-server/pull/4522), [#7516](https://github.com/rabbitmq/rabbitmq-server/pull/7516) * Reduced peak memory footprint of quorum queues. -- cgit v1.2.1