Github user mtaylor commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/1232#discussion_r113885079
--- Diff: 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.
--- End diff --
+1 @franz1981 I think we already discussed this on IRC but, having the
global-max-size being 1/5th of heap by default for the out of the box
configuration seems like overkill. These settings are meant to target a
particular use case.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
