Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Tue, 12 Nov 2013 18:12:19 +0000 (UTC)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.12665071.1377190626266.58996.1384279939646@arcas>
In-Reply-To: <JIRA.12665071.1377190626266@arcas>
References: <JIRA.12665071.1377190626266@arcas>
Subject: [jira] [Updated] (MAVIBOT-11) Add a cache to replace the
 weakReferences
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAVIBOT-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated MAVIBOT-11:
-------------------------------------

    Fix Version/s:     (was: 1.0.0-M2)
                   1.0.0-M3

> Add a cache to replace the weakReferences
> -----------------------------------------
>
>                 Key: MAVIBOT-11
>                 URL: https://issues.apache.org/jira/browse/MAVIBOT-11
>             Project: Mavibot
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-M1
>            Reporter: Emmanuel Lecharny
>            Assignee: Emmanuel Lecharny
>            Priority: Critical
>             Fix For: 1.0.0-M3
>
>
> We currently use a WeakReference to hold elements in memory. This is convenient, but when we have exhausted the memory, the GC takes forever to reclaim the weakReferences, slowing down the code up to a point it's unusable.
> We should rather use a LRU Cache to store a limited amount of elements, and make it configurable.
> We should keep the WeakReferences for those having enough memory. (to be discussed)


--
This message was sent by Atlassian JIRA
(v6.1#6144)