You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Stephen Darlington (Jira)" <ji...@apache.org> on 2020/10/07 13:10:00 UTC

[jira] [Updated] (IGNITE-13503) On-heap cache eviction policy based on available memory rather than number of records

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

Stephen Darlington updated IGNITE-13503:
----------------------------------------
    Summary: On-heap cache eviction policy based on available memory rather than number of records  (was: On-heap cache eviction policy based on size rather than number of records)

> On-heap cache eviction policy based on available memory rather than number of records
> -------------------------------------------------------------------------------------
>
>                 Key: IGNITE-13503
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13503
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Stephen Darlington
>            Priority: Minor
>
> Currently, you can set the maximum size of an on-heap cache strictly by the number of records it holds. In cases where records vary substantially in size this could result in the cache being far bigger or far smaller than anticipated.
> It would be nice to have the option to specify a maximum size in bytes.



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