You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Scott Blum (JIRA)" <ji...@apache.org> on 2016/11/30 01:24:58 UTC

[jira] [Commented] (SOLR-7282) Cache config or index schema objects by configset and share them across cores

    [ https://issues.apache.org/jira/browse/SOLR-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707159#comment-15707159 ] 

Scott Blum commented on SOLR-7282:
----------------------------------

Could we cache by content hash?  Then even collections that physically don't share the same configset but whose contents are identical could share config.

> Cache config or index schema objects by configset and share them across cores
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-7282
>                 URL: https://issues.apache.org/jira/browse/SOLR-7282
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Noble Paul
>             Fix For: 5.2, 6.0
>
>         Attachments: SOLR-7282.patch
>
>
> Sharing schema and config objects has been known to improve startup performance when a large number of cores are on the same box (See http://wiki.apache.org/solr/LotsOfCores).Damien also saw improvements to cluster startup speed upon caching the index schema in SOLR-7191.
> Now that SolrCloud configuration is based on config sets in ZK, we should explore how we can minimize config/schema parsing for each core in a way that is compatible with the recent/planned changes in the config and schema APIs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org