[
https://issues.apache.org/jira/browse/SOLR-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-13433:
-----------------------------------------
Description:
One can enable maxRamMB on filter and query result caches and in that case the
ram usage of the caches is maintained and exposed as well as the entries are
evicted according to overall ram usage. However, the two features need not be
coupled together i.e. tracking and exposing ram usage can be a separate feature
from evicting by ram usage.
I propose to add an optional {{showRamUsage}} to filter and query result caches
that can be enabled to expose ram size of the cache. The default will be off
but if {{maxRamMB}} is set then {{showRamUsage}} is automatically set to true.
was:
One can enable maxRamMB on filter and query result caches and in that case the
ram usage of the caches is maintained and exposed as well as the entries are
evicted according to overall ram usage. However, the two features need not be
coupled together i.e. tracking and exposing ram usage can be a separate feature
from evicting by ram usage.
I propose to add an optional {{showRamUsage}} to filter and query result caches
that can be enabled to expose ram size of the cache. The default will be off
but if {{maxRamMB} is set then {{showRamUsage}} is automatically set to true.
> Optionally track and expose ram usage for filter and query result caches
> ------------------------------------------------------------------------
>
> Key: SOLR-13433
> URL: https://issues.apache.org/jira/browse/SOLR-13433
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Fix For: 8.1, master (9.0)
>
>
> One can enable maxRamMB on filter and query result caches and in that case
> the ram usage of the caches is maintained and exposed as well as the entries
> are evicted according to overall ram usage. However, the two features need
> not be coupled together i.e. tracking and exposing ram usage can be a
> separate feature from evicting by ram usage.
> I propose to add an optional {{showRamUsage}} to filter and query result
> caches that can be enabled to expose ram size of the cache. The default will
> be off but if {{maxRamMB}} is set then {{showRamUsage}} is automatically set
> to true.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
