diff options
| author | Matthew Sackman <matthew@rabbitmq.com> | 2010-11-09 17:18:08 +0000 |
|---|---|---|
| committer | Matthew Sackman <matthew@rabbitmq.com> | 2010-11-09 17:18:08 +0000 |
| commit | fb9bf1afff3699236b0af404c70359c0d42483e1 (patch) | |
| tree | 5e478664a8a5c97e431e75371b8645a5f0b3860a | |
| parent | f77cffcd78044c083a73884c5d2a8265c7625a67 (diff) | |
| download | rabbitmq-server-git-fb9bf1afff3699236b0af404c70359c0d42483e1.tar.gz | |
Updating outdated comment
| -rw-r--r-- | src/rabbit_memory_monitor.erl | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/src/rabbit_memory_monitor.erl b/src/rabbit_memory_monitor.erl index f87b62713a..bb4d77a4f7 100644 --- a/src/rabbit_memory_monitor.erl +++ b/src/rabbit_memory_monitor.erl @@ -63,8 +63,9 @@ %% have some space for when the queues don't quite respond as fast as %% we would like, or when there is buffering going on in other parts %% of the system. In short, we aim to stay some distance away from -%% when the memory alarms will go off, which cause channel.flow. -%% Note that all other Thresholds are relative to this scaling. +%% when the memory alarms will go off, which cause backpressure (of +%% some sort) on producers. Note that all other Thresholds are +%% relative to this scaling. -define(MEMORY_LIMIT_SCALING, 0.4). -define(LIMIT_THRESHOLD, 0.5). %% don't limit queues when mem use is < this |