camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Baker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10432) concurrentlinkedhashmap used by LRU cache consumes 100MB memory on 1024 core Solaris T5
Date Tue, 01 Nov 2016 16:12:58 GMT

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

Matt Baker commented on CAMEL-10432:
------------------------------------

this may have already been fixed but would require an update to the ConcurrentLinkedHashMap
1.4.2.

https://github.com/ben-manes/concurrentlinkedhashmap/issues/43

> concurrentlinkedhashmap used by LRU cache consumes 100MB memory on 1024 core Solaris
T5
> ---------------------------------------------------------------------------------------
>
>                 Key: CAMEL-10432
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10432
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.17.1
>         Environment: Solaris T5 1024 core machine
> java 1.7.045
>            Reporter: Matt Baker
>
> Cloned from: AMQ-6492
> On a Solaris T5 with 1024 cores, the amount of memory used by LRUCache which in turn
is using ConcurrentLinkedHashMap from 
> https://github.com/ben-manes/concurrentlinkedhashmap
> consumes about 20MB of memory.  In my install this correlates to over 300MB of memory.
> concurrentlinkedhashmap allocates memory based on CPU count, with no upper limit, so
each instance of LRUCache in memory consumes more memory than is really needed.
> See AMQ-6492 for screenshots (didn't want to copy/paste them here)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message