summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorMichael Klishin <mklishin@pivotal.io>2017-02-05 14:41:40 +0300
committerMichael Klishin <mklishin@pivotal.io>2017-02-05 14:41:40 +0300
commit2f3fb8023ba1f535b13f4deb97106c08b78bc1d9 (patch)
tree9ed15d94bae7641041c4a0974857618d866e1182 /scripts
parent3c32d7ed3ebf6d756a3e61a84cbeebc7394fc7f4 (diff)
downloadrabbitmq-server-git-2f3fb8023ba1f535b13f4deb97106c08b78bc1d9.tar.gz
Disable background GC by default; bump credit flow defaults
Quite a bit of evidence of different kinds of workloads suggest that background GC does not contribute meaningfully to reducing node RAM usage on most of them. It does, however, on each run produce a massive spike in VM and CPU context switches, causing latency spikes. Some users report that running without background GC cuts their latency to a half or even a third. Multi-hour stress tests that max out all node CPU cores suggest that our current credit_flow default can still be bumped safely, reducing the amount of time publishers are throttled and making publisher latency and node's observed message throughput more predictable.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions