activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-6940) Significant memory footprint increase from 5.8.0 to 5.15.3
Date Wed, 28 Mar 2018 22:41:00 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418213#comment-16418213
] 

Christopher L. Shannon edited comment on AMQ-6940 at 3/28/18 10:40 PM:
-----------------------------------------------------------------------

The reason why this has never come up is because you are running on a very small JVM for the
number of consumers and producers you have.  600 megabytes of memory is pretty small given
the number of producers and consumers is over 8000.  So yes the feature is not going to scale
without proper memory allocation. The short term solution is to simply increase your heap
size.

A more permanent fix is to add a flag to the policy configuration to disable the inflight
statistics on TopicSubscription so that the dispatched array doesn't collect objects anymore
(basically what you already did).  This is something that can be added for the next patch
release so you can disable the statistics.

 

 


was (Author: christopher.l.shannon):
The reason why this has never come up is because you are running on a very small JVM for the
number of consumers and producers you have.  600 megabytes of memory is pretty small given
the number of producers and consumers is over 8000.  So yes the feature is not going to scale
without proper memory allocation. The short term solution is to simply increase your heap
size.

A more permanent fix would is to add a flag to the policy configuration to disable the inflight
statistics on TopicSubscription so that the dispatched array doesn't collect objects anymore
(basically what you already did).  This is something that can be added for the next patch
release so you can disable the statistics.

 

 

> 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)

Mime
View raw message