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.

Sign up for GitHub

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

Jump to bottom

Set the default vm_memory_high_watermark to 0.6 (backport #12161) #12162

Merged
merged 1 commit into from
Aug 29, 2024
Merged

Set the default vm_memory_high_watermark to 0.6 (backport #12161) #12162

merged 1 commit into from
Aug 29, 2024

Commits on Aug 29, 2024

  1. Set the default vm_memory_high_watermark to 0.6 (#12161) 

    The default of 0.4 was very conservative even when it was
set years ago. Since then:
- we moved to CQv2, which have much more predictable memory usage than (non-lazy) CQv1 used to
- we removed CQ mirroring which caused large sudden memory spikes in some situations
- we removed the option to store message payload in memory in quorum queues

For the past two years or so, we've been running all our internal tests and benchmarks
using the value of 0.8 with no OOMkills at all (note: we do this on
Kubernetes where the Cluster Operators overrides the available memory
levaing some additional headroom, but effectively we are still using  more than
0.6 of memory).

(cherry picked from commit 8a03975)
    @mkuratczyk @mergify
    mkuratczyk authored and mergify[bot] committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    716703c View commit details
    Browse the repository at this point in the history