[
https://issues.apache.org/jira/browse/SOLR-8349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142190#comment-15142190
]
David Smiley commented on SOLR-8349:
------------------------------------
I put a little more thought into this issue now. The cache at the
CoreContainer makes sense but I'm not convinced that the Lucene layer needs a
new abstraction. Instead, I think Solr could be enhanced to load some analysis
components into this CoreContainer cache. The question is which ones? Not
all... some components will be refer to resources that are local to a SolrCore.
I'm not sure how easy it would be for Solr to detect that automatically;
probably not easy. That leaves the possibility of a new attribute on the core
to designate it as globally shared. What do you think?
> Allow sharing of large in memory data structures across cores
> -------------------------------------------------------------
>
> Key: SOLR-8349
> URL: https://issues.apache.org/jira/browse/SOLR-8349
> Project: Solr
> Issue Type: Improvement
> Components: Server
> Affects Versions: 5.3
> Reporter: Gus Heck
> Attachments: SOLR-8349.patch
>
>
> In some cases search components or analysis classes may utilize a large
> dictionary or other in-memory structure. When multiple cores are loaded with
> identical configurations utilizing this large in memory structure, each core
> holds it's own copy in memory. This has been noted in the past and a specific
> case reported in SOLR-3443. This patch provides a generalized capability, and
> if accepted, this capability will then be used to fix SOLR-3443.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
