[
https://issues.apache.org/jira/browse/GEODE-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238625#comment-16238625
]
ASF GitHub Bot commented on GEODE-3622:
---------------------------------------
nreich opened a new pull request #1017: GEODE-3622: Implement new algorithm for
eviction
URL: https://github.com/apache/geode/pull/1017
* New algorithm utilized asynchronous scanning mechanims for
maintaining recently used entry information
* Move region entries into their own package
* Organize eviction code into new eviction package
* General refactoring of eviction classes
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> The first HeapLRU evictions on large region can consume high amounts of CPU
> ---------------------------------------------------------------------------
>
> Key: GEODE-3622
> URL: https://issues.apache.org/jira/browse/GEODE-3622
> Project: Geode
> Issue Type: Bug
> Components: eviction
> Reporter: Darrel Schneider
> Assignee: Kirk Lund
> Priority: Major
>
> If you have a region configured for HeapLRU eviction and are able to put a
> large number of entries in it before hitting the eviction threshold, then the
> first evictions will consume much more CPU than subsequent evictions. The
> reason for this is that the eviction list is not initialized until the first
> eviction is done. At that time a scan is done of all the existing entries
> marking each one as not having been recently used. This can touch a large
> number of memory pages and also hits some common synchronization locks. You
> can see that this is happening by looking at the HeapLRUStats.lruEvaluations
> stat.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
