diff options
| author | Matthew Sackman <matthew@lshift.net> | 2009-12-03 17:55:34 +0000 |
|---|---|---|
| committer | Matthew Sackman <matthew@lshift.net> | 2009-12-03 17:55:34 +0000 |
| commit | d5522a16fe8528f494a38ab2c6350e731fddab3a (patch) | |
| tree | bd936aed1764070aa272fc7aa76c172e00693e50 | |
| parent | d1fd1f4acd9f852b2a1779a4008809f3bd32d292 (diff) | |
| download | rabbitmq-server-git-d5522a16fe8528f494a38ab2c6350e731fddab3a.tar.gz | |
With R13B03, it would appear we need to be slightly more hesitant: currently I'm seeing the memory limits being hit and the queue duration is still fairly large. Whilst it does eventually fall, setting this scalar a little lower should help. However, this will probably need tweaking again, once we've moved away from ets in the msg_store
| -rw-r--r-- | src/rabbit_memory_monitor.erl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/rabbit_memory_monitor.erl b/src/rabbit_memory_monitor.erl index 5c0b2daaa3..d6693d95a9 100644 --- a/src/rabbit_memory_monitor.erl +++ b/src/rabbit_memory_monitor.erl @@ -65,7 +65,7 @@ %% 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. --define(MEMORY_LIMIT_SCALING, 0.6). +-define(MEMORY_LIMIT_SCALING, 0.4). -define(LIMIT_THRESHOLD, 0.5). %% don't limit queues when mem use is < this |