[
https://issues.apache.org/jira/browse/IGNITE-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov updated IGNITE-5874:
-------------------------------
Description:
TTL expire times for entries are stored in PendingEntriesTree, which is
singleton for cache. When expiration occurs, all system threads iterate through
the tree in order to remove expired entries. Iterating through single tree
causes contention and perfomance loss.
Related performance issue: https://issues.apache.org/jira/browse/IGNITE-5793
We should keep instance of PendingEntriesTree for each partition, like we do
for CacheDataTree.
was:
TTL expire times for entries are stored in PendingEntriesTree, which is
singleton for cache. When expiration occurs, all system threads iterate through
the tree in order to remove expired entries. Iterating through single tree
causes contention and perfomance loss. Related performance issue:
https://issues.apache.org/jira/browse/IGNITE-5793
We should keep instance of PendingEntriesTree for each partition, like we do
for CacheDataTree.
> Store TTL expire times in B+ tree on per-partition basis
> --------------------------------------------------------
>
> Key: IGNITE-5874
> URL: https://issues.apache.org/jira/browse/IGNITE-5874
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 2.1
> Reporter: Ivan Rakov
> Fix For: 2.2
>
>
> TTL expire times for entries are stored in PendingEntriesTree, which is
> singleton for cache. When expiration occurs, all system threads iterate
> through the tree in order to remove expired entries. Iterating through single
> tree causes contention and perfomance loss.
> Related performance issue: https://issues.apache.org/jira/browse/IGNITE-5793
> We should keep instance of PendingEntriesTree for each partition, like we do
> for CacheDataTree.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
