diff options
| author | Michael Klishin <mklishin@pivotal.io> | 2017-07-26 19:59:32 +0300 |
|---|---|---|
| committer | Michael Klishin <mklishin@pivotal.io> | 2017-07-26 19:59:32 +0300 |
| commit | 7f30e61770ce6ff1e1105915e6bd012b388aaaa8 (patch) | |
| tree | c5fdb16f62942c79508febde2769786320e5a7ab | |
| parent | 32d7797fa19885d42d2afd3d0de184863af34051 (diff) | |
| download | rabbitmq-server-git-7f30e61770ce6ff1e1105915e6bd012b388aaaa8.tar.gz | |
Update new style config example as well
| -rw-r--r-- | docs/rabbitmq.conf.example | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/docs/rabbitmq.conf.example b/docs/rabbitmq.conf.example index e4c2fff92a..68ce59326e 100644 --- a/docs/rabbitmq.conf.example +++ b/docs/rabbitmq.conf.example @@ -252,8 +252,18 @@ ## Fraction of the high watermark limit at which queues start to ## page message out to disc in order to free up memory. +## For example, when vm_memory_high_watermark is set to 0.4 and this value is set to 0.5, +## paging can begin as early as when 20% of total available RAM is used by the node. ## -## Values greater than 0.9 can be dangerous and should be used carefully. +## Values greater than 1.0 can be dangerous and should be used carefully. +## +## One alternative to this is to use durable queues and publish messages +## as persistent (delivery mode = 2). With this combination queues will +## move messages to disk much more rapidly. +## +## Another alternative is to configure queues to page all messages (both +## persistent and transient) to disk as quickly +## as possible, see http://www.rabbitmq.com/lazy-queues.html. ## # vm_memory_high_watermark_paging_ratio = 0.5 |