[
https://issues.apache.org/jira/browse/IGNITE-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839490#comment-15839490
]
ASF GitHub Bot commented on IGNITE-4552:
----------------------------------------
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/1465
IGNITE-4552 support eviction for dhtLocalPartition remove queue
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4552
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1465.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1465
----
commit be22a73c3b47ed898c1dc8c3957d672bf8f02ae6
Author: Evgeny Stanilovskiy <[email protected]>
Date: 2017-01-25T15:15:50Z
IGNITE-4552 support eviction for dhtLocalPartition remove queue
----
> Optimize GridDhtLocalPartition.rmvQueue
> ---------------------------------------
>
> Key: IGNITE-4552
> URL: https://issues.apache.org/jira/browse/IGNITE-4552
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.6
> Reporter: Alexei Scherbakov
> Assignee: Stanilovsky Evgeny
> Fix For: 2.0
>
> Attachments: Screenshot_20170124_155355.png
>
>
> Current implementation stores deferred entry removals in rmvQueue for
> consistency guaranties.
> This can lead to significant heap over-usage(I observed several Gbs) in case
> of many caches with removals, because currently queue is cleared lazily after
> reaching max capacity(200_000 by default).
> This can be mitigated by using lower IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE,
> but can lead to consistency issues in case of frequent cache updates.
> Possible optimizations:
> * Use single fixed size queue per all caches to overcome limitations of
> IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE workaround.
> * Do queue cleaning in background
> * Move queue to an off-heap.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)