diff options
| author | Michael Klishin <michael@rabbitmq.com> | 2013-10-28 18:01:49 +0400 |
|---|---|---|
| committer | Michael Klishin <michael@rabbitmq.com> | 2013-10-28 18:01:49 +0400 |
| commit | 0e36bc181d938409e09c96ee00facee29b00adbe (patch) | |
| tree | 776ce1421c202bf1ecf377ce968e24bad0a5ad3c | |
| parent | 659798082141622b232aa298edc3cbdc88648048 (diff) | |
| download | rabbitmq-server-bug25845.tar.gz | |
Use 580 seconds as default heartbeat intervalbug25845
240 seconds gives a theoretiacl 2.5 decrease in server load
(over the previous default of 600 seconds), while
580 gives a ~3% increase.
In a test that involved watching CPU usage 1000 idle connections
I observe effectively no difference between 600 and 580 values.
580 seconds is enough to cause network activity every 290 (< 300) seconds
and hopefully make F5 gear with default timeout settings happy.
| -rw-r--r-- | ebin/rabbit_app.in | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ebin/rabbit_app.in b/ebin/rabbit_app.in index 86f792e2..a10bad45 100644 --- a/ebin/rabbit_app.in +++ b/ebin/rabbit_app.in @@ -25,7 +25,7 @@ %% 0 ("no limit") would make a better default, but that %% breaks the QPid Java client {frame_max, 131072}, - {heartbeat, 240}, + {heartbeat, 580}, {msg_store_file_size_limit, 16777216}, {queue_index_max_journal_entries, 65536}, {default_user, <<"guest">>}, |