[jira] [Updated] (IGNITE-3621) Make GridCacheTtlManager singleton

["Maxim Muzafarov (Jira)" <ji...@apache.org>]

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

Maxim Muzafarov updated IGNITE-3621:
------------------------------------
    Fix Version/s: 2.8

> Make GridCacheTtlManager singleton
> ----------------------------------
>
>                 Key: IGNITE-3621
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3621
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.6
>            Reporter: Eduard Shangareev
>            Priority: Major
>              Labels: performance
>             Fix For: 2.8
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Now every cache has own TTL manager, which creates CleanupWorker = new extra thread. This can cause to extra hundreds of threads (redundant context switches = performance penalty).
> Also, under IGNITE-3513 every put can enter critical section to notify worker. Obviously, it is not good from performance point of view.
> So, my proposal is next:
> 1. Expiration should be done on every cache action (on exit thread which updates cache should invoke {{expire}}).
> 2. TtlManager will exist only in one instance.
> 3. CleanupWorker will be the only backup if there is no cache activity. It will wake up with some period to check for work (500 ms, for example).
> Moreover, now we keep on-heap pending entries even if a cache is kept off-head. At least, this issue needs discussion.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)