[
https://issues.apache.org/jira/browse/IGNITE-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715015#comment-16715015
]
ASF GitHub Bot commented on IGNITE-4552:
----------------------------------------
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/1481
> 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
> Priority: Major
> Fix For: 2.0
>
> Attachments: Plot_ThroughputLatencyProbe_01_20170203_1.png,
> Plot_ThroughputLatencyProbe_01_31_origin.png,
> Plot_ThroughputLatencyProbe_01_4552_mine.png,
> Plot_ThroughputLatencyProbe_01_mine.png,
> Plot_ThroughputLatencyProbe_01_mine_3node.png,
> Plot_ThroughputLatencyProbe_01_origin.png,
> Plot_ThroughputLatencyProbe_01_origin_3node.png,
> Screenshot_20170124_155355.png, benchmark-put-remove-simultaneously.properties
>
>
> 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
(v7.6.3#76005)
