You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Andrzej Bialecki (JIRA)" <ji...@apache.org> on 2019/07/31 09:23:01 UTC
[jira] [Commented] (SOLR-13433) Optionally track and expose ram
usage for filter and query result caches
[ https://issues.apache.org/jira/browse/SOLR-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896974#comment-16896974 ]
Andrzej Bialecki commented on SOLR-13433:
------------------------------------------
With the exception of the boolean flag this functionality has been implemented as a part of SOLR-13558.
Tracking this value at all times has negligible cost but it provides useful information about the actual cache RAM consumption even when {{maxRamMB}} is not in use.
> 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
> Reporter: Shalin Shekhar Mangar
> Assignee: Andrzej Bialecki
> Priority: Major
> Fix For: master (9.0), 8.2
>
>
> 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.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org