[ https://issues.apache.org/jira/browse/SOLR-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846298#comment-17846298 ]
David Smiley commented on SOLR-3443: ------------------------------------ Where I work, we have both massive resources in our schema and also thousands of cores per node. The memory (and time to load a schema) problem is easily solved with [shareSchema in solr.xml|https://solr.apache.org/guide/solr/latest/configuration-guide/configuring-solr-xml.html] instead of narrow point-solutions for specific resources. > Optimize hunspell dictionary loading with multiple cores > -------------------------------------------------------- > > Key: SOLR-3443 > URL: https://issues.apache.org/jira/browse/SOLR-3443 > Project: Solr > Issue Type: Improvement > Reporter: Luca Cavanna > Priority: Major > Attachments: SOLR-3443.patch, Screen Shot 2015-11-29 at 9.52.06 AM.png > > > The Hunspell dictionary is actually loaded into memory. Each core using > hunspell loads its own dictionary, no matter if all the cores are using the > same dictionary files. As a result, the same dictionary is loaded into memory > multiple times, once for each core. I think we should share those > dictionaries between all cores in order to optimize the memory usage. In > fact, let's say a dictionary takes 20MB into memory (this is what I > detected), if you have 20 cores you are going to use 400MB only for > dictionaries, which doesn't seem a good idea to me. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org