diff options
| author | Matthew Sackman <matthew@lshift.net> | 2009-11-26 15:06:01 +0000 |
|---|---|---|
| committer | Matthew Sackman <matthew@lshift.net> | 2009-11-26 15:06:01 +0000 |
| commit | b38451168cacb2e93e96a72dbc5d4ad6ab1668ad (patch) | |
| tree | 5d7f74243a32cc37adb3a610efd865deac403269 /src | |
| parent | 4578759320d14668519bdb4d89439f48041074e3 (diff) | |
| download | rabbitmq-server-git-b38451168cacb2e93e96a72dbc5d4ad6ab1668ad.tar.gz | |
s/b(.)t/s\1m/
Diffstat (limited to 'src')
| -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 1e84d64d7a..0389219354 100644 --- a/src/rabbit_memory_monitor.erl +++ b/src/rabbit_memory_monitor.erl @@ -81,7 +81,7 @@ %% told a duration of infinity (eg if less than LIMIT_THRESHOLD memory %% is being used). Subsequently, the memory-monitor can calculate the %% desired duration as zero, or close to zero (eg now more memory is -%% being used, but the sum of durations is very small). If it is a +%% being used, and the sum of durations is very small). If it is a %% fast moving queue, telling it a very small value will badly hurt %% it, unnecessarily: a fast moving queue will often oscillate between %% being empty and having a few thousand msgs in it, representing a |