diff options
| author | Michael Klishin <mklishin@pivotal.io> | 2018-03-21 10:07:07 +0300 |
|---|---|---|
| committer | Michael Klishin <mklishin@pivotal.io> | 2018-03-21 10:07:07 +0300 |
| commit | bb36e18a0ab25117ca8ccf3aecd58bdd3985006b (patch) | |
| tree | ea0edc635b9846225bb4428a61c926dbbb4258f5 /docs/rabbitmq.config.example | |
| parent | 2ae6ba6578baaef95657d1b90470f848d464eeb7 (diff) | |
| download | rabbitmq-server-git-bb36e18a0ab25117ca8ccf3aecd58bdd3985006b.tar.gz | |
Improve background_gc docs in example config files
To make it clearer that memory breakdown analysis must
be done formed. "Don't guess, collect data".
Diffstat (limited to 'docs/rabbitmq.config.example')
| -rw-r--r-- | docs/rabbitmq.config.example | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/docs/rabbitmq.config.example b/docs/rabbitmq.config.example index 3d41ae138c..9ee9a352be 100644 --- a/docs/rabbitmq.config.example +++ b/docs/rabbitmq.config.example @@ -471,7 +471,15 @@ %% %% {disk_monitor_failure_retry_interval, 120000}, - %% Whether or not to enable background GC. + %% Whether or not to enable background periodic forced GC runs for all + %% Erlang processes on the node in "waiting" state. + %% + %% Disabling background GC may reduce latency for client operations, + %% keeping it enabled may reduce median RAM usage by the binary heap + %% (see https://www.erlang-solutions.com/blog/erlang-garbage-collector.html). + %% + %% Before enabling this option, please take a look at the memory + %% breakdown (http://www.rabbitmq.com/memory-use.html). %% %% {background_gc_enabled, false}, |