[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695315#comment-16695315
]
Cetra Free commented on SOLR-13003:
-----------------------------------
With regards to {{FastLRUCache}}: the actual accounting implementation is in
{{ConcurrentLRUCache}} which appears to be doing the right thing. But the
issue is the size comparison, so I don't think swapping would help. I will give
it a shot regardless.
I've noticed the QueryResultKey is greater than 75kb of memory per key, which
is much greater size than the value.
I will try out the patched version from Shawn & see if I can trigger it and get
some stats out.
> 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, solr-core-7.3.1-SNAPSHOT.jar, 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: [email protected]
For additional commands, e-mail: [email protected]
