[
https://issues.apache.org/jira/browse/SOLR-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated SOLR-3486:
-------------------------------
Attachment: SOLR-3486.patch
Hi Shawn,
I modified the patch in order to make it easier to add this functionality to
other cache implementations. All you need to do for SOLR-3393 to support
maximum memory size is to split your implementation into a LFU map (a regular
map, with no evictions) which iterates (entrySet().iterator()) in frequency
order and a LFU cache (that will probably extend or wrap this LFU map). Then to
have a LFU cache with a fixed max mem size, just wrap your LFU map into a new
SizableCache instance.
> The memory size of Solr caches should be configurable
> -----------------------------------------------------
>
> Key: SOLR-3486
> URL: https://issues.apache.org/jira/browse/SOLR-3486
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: SOLR-3486.patch, SOLR-3486.patch
>
>
> It is currently possible to configure the sizes of Solr caches based on the
> number of entries of the cache. The problem is that the memory size of cached
> values may vary a lot over time (depending on IndexReader.maxDoc and the
> queries that are run) although the JVM heap size does not.
> Having a configurable max size in bytes would also help optimize cache
> utilization, making it possible to store more values provided that they have
> a small memory footprint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
