[
https://issues.apache.org/jira/browse/AMQ-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418237#comment-16418237
]
Johno Crawford edited comment on AMQ-6940 at 3/29/18 8:21 AM:
--------------------------------------------------------------
I don't agree that 600 megabytes of memory is too little for over 8k producers
and consumers, prior to 5.15.3 the JVM took an average of 100mb of heap (150mb
max). To be brutally honest I believe the implementation is broken, apart from
it taking so much memory, it should not be storing the actual messages and
their payloads for so long (or even at all for that matter) even if it is a non
persistent topic, the consumer is not slow and the messages have been delivered
the messages remain in the dispatched array until updateStatsOnAck is invoked
which is seldom..
was (Author: johno):
I don't agree that 600 megabytes of memory is too little for over 8k producers
and consumers, prior to 5.15.3 the JVM took an average of 100mb of heap (150mb
max). To be brutally honest I believe the implementation is broken, apart from
it taking so much memory, it should not be storing the actual messages and
their payloads for so long (or even at all for that matter) even if it is a non
persistent topic, the consumer is not slow and the messages have been delivered
the messages remain in the dispatched array until updateStatsOnAck is invoked..
> Significant memory footprint increase from 5.8.0 to 5.15.3
> ----------------------------------------------------------
>
> Key: AMQ-6940
> URL: https://issues.apache.org/jira/browse/AMQ-6940
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.15.3
> Environment: Java jdk1.8.0_144
> OS Linux 4.4.19-29.55.amzn1.x86_64
> Reporter: Johno Crawford
> Priority: Major
> Attachments: activemq.xml, amq_heap2.png, messageid_analysis.png
>
>
> Recently we upgraded from 5.8.0 to 5.15.3 on one of our environments and
> found the broker running out of memory with the old broker configurations.
> I suspect this may be related to the new inflight message size calculation
> but haven't been able to create a reproducer just yet.
> Broker JVM running with opts
> {code:java}
> -Xss256k -Xms600m -Xmx600m -Xmn128m -Dfile.encoding=ISO-8859-1
> -Dlog4j.watchDelay=60000 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps
> -XX:+PrintGCDateStamps -XX:+PrintPromotionFailure -XX:PrintFLSStatistics=1
> -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+PrintClassHistogram -verbose:gc
> -Dsun.rmi.dgc.client.gcInterval=7200000
> -Dsun.rmi.dgc.server.gcInterval=7200000
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
