[
https://issues.apache.org/jira/browse/IGNITE-13503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Darlington updated IGNITE-13503:
----------------------------------------
Description:
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 ability to use available memory, for example using
Java's soft references.
was:
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.
> 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 ability to use available memory, for example
> using Java's soft references.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
