You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by ma...@apache.org on 2017/04/28 09:29:19 UTC
[2/2] activemq-artemis git commit: ARTEMIS-1131 Configure optimal GC
settings
ARTEMIS-1131 Configure optimal GC settings
Project: http://git-wip-us.apache.org/repos/asf/activemq-artemis/repo
Commit: http://git-wip-us.apache.org/repos/asf/activemq-artemis/commit/8cef9221
Tree: http://git-wip-us.apache.org/repos/asf/activemq-artemis/tree/8cef9221
Diff: http://git-wip-us.apache.org/repos/asf/activemq-artemis/diff/8cef9221
Branch: refs/heads/master
Commit: 8cef9221f4c9bde04d8e0a4f99b57ee8732367e9
Parents: 0e800d8
Author: Francesco Nigro <ni...@gmail.com>
Authored: Thu Apr 27 16:50:11 2017 +0200
Committer: Martyn Taylor <mt...@redhat.com>
Committed: Fri Apr 28 10:29:01 2017 +0100
----------------------------------------------------------------------
docs/user-manual/en/perf-tuning.md | 8 ++++++++
1 file changed, 8 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/activemq-artemis/blob/8cef9221/docs/user-manual/en/perf-tuning.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/perf-tuning.md b/docs/user-manual/en/perf-tuning.md
index e05578d..f131a15 100644
--- a/docs/user-manual/en/perf-tuning.md
+++ b/docs/user-manual/en/perf-tuning.md
@@ -206,6 +206,14 @@ tunings won't apply to JDKs from other providers (e.g. IBM or JRockit)
of your queues and the size and number of your messages. Use the JVM
arguments `-Xms` and `-Xmx` to set server available RAM. We
recommend setting them to the same high value.
+
+ When under periods of high load, it is likely that Artemis will be generating
+ and destroying lots of objects. This can result in a build up of stale objects.
+ To reduce the chance of running out of memory and causing a full GC
+ (which may introduce pauses and unintentional behaviour), it is recommended that the
+ max heap size (`-Xmx`) for the JVM is set at least to 5 x the `global-max-size` of the broker.
+ As an example, in a situation where the broker is under high load and running
+ with a `global-max-size` of 1GB, it is recommended the the max heap size is set to 5GB.
- Aggressive options. Different JVMs provide different sets of JVM
tuning parameters, for the Sun Hotspot JVM the full list of options