diff options
| author | Michael Klishin <michael@novemberain.com> | 2017-07-28 21:37:42 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-07-28 21:37:42 +0300 |
| commit | e84ba4ca9329243879f51bf147f079519171c81f (patch) | |
| tree | 566e8a702fe706a0e4cfaa67f5ed7b2adc932d83 /docs | |
| parent | 118666d7caba0e494ec3f8144c0a35e12130a9a1 (diff) | |
| parent | 77101e7fadaac0bf12b862c6c6cf48e08eb97e4b (diff) | |
| download | rabbitmq-server-git-e84ba4ca9329243879f51bf147f079519171c81f.tar.gz | |
Merge branch 'master' into fix-travis-ci-build
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/rabbitmq.conf.example | 12 | ||||
| -rw-r--r-- | docs/rabbitmq.config.example | 12 |
2 files changed, 22 insertions, 2 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 diff --git a/docs/rabbitmq.config.example b/docs/rabbitmq.config.example index 4135c5053c..b7f08afc78 100644 --- a/docs/rabbitmq.config.example +++ b/docs/rabbitmq.config.example @@ -236,8 +236,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}, |