[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694228#comment-16694228
]
Shawn Heisey commented on SOLR-13003:
-------------------------------------
Attached a patch for adding logging. Will attach a custom jar when Solr
finishes compiling.
[~cetra3], you're in the best position to test this. I no longer have access
to Solr servers that I can change at will, so it's difficult for me to do this.
I would suggest that when testing this, you only have one of Solr's caches set
up with maxRamMB, define all the others with the usual "size" parameters. If
you could provide a file with a typical search response from Solr so we can see
how much data a response contains, that would be helpful. If you choose to do
testing with the filterCache, we will need to know how many docs (maxDoc, not
numDoc) the core contains.
> Query Result Cache does not honour maxRamBytes parameter
> --------------------------------------------------------
>
> Key: SOLR-13003
> URL: https://issues.apache.org/jira/browse/SOLR-13003
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.3.1
> Reporter: Cetra Free
> Priority: Major
> Attachments: CLRU-logging.patch, lrucacheexpanded.png,
> lrucachemaxmb.png, solrconfig.xml
>
>
> When using the maxRamBytes parameter with the queryResultCache directive, we
> have seen the retained size of the cache orders of magnitude larger than what
> is configured.
> Please see attached VisualVM output which shows the retained size is about
> 1.5gb, but the maxRamBytes is set to 64mb.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
