[
https://issues.apache.org/jira/browse/ARTEMIS-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988339#comment-15988339
]
ASF GitHub Bot commented on ARTEMIS-1131:
-----------------------------------------
Github user franz1981 commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/1232#discussion_r113867388
--- 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 --
It is not a bad idea IMHO, but these hints are supposed to work best when a
user is near 100% sure that the broker will be hammered by requests (without
any expire queue) while retaining in memory the whole `global-max-size` bytes...
I've the impression that raising the requirements (5 times more!) for the
common use case to satisfy the uncommon ones could be to too restrictive, wdyt?
> Configure optimal GC settings
> -----------------------------
>
> Key: ARTEMIS-1131
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1131
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Minor
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
