You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2019/04/29 06:30:00 UTC

[jira] [Created] (SOLR-13433) Optionally track and expose ram usage for filter and query result caches

Shalin Shekhar Mangar created SOLR-13433:
--------------------------------------------

             Summary: 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
             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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org