You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2008/12/16 10:04:44 UTC
[jira] Created: (SOLR-919) Cache and reuse the DOM object of
solrconfig.xml
Cache and reuse the DOM object of solrconfig.xml
------------------------------------------------
Key: SOLR-919
URL: https://issues.apache.org/jira/browse/SOLR-919
Project: Solr
Issue Type: Improvement
Reporter: Noble Paul
If there are 1000's of cores the no:of times we need to load and parse the solrconfig.xml is going to be very expensive. In such a case we may mostly have same solrconfig.xml with some core properties embedded
The solution is , if the location of the xml file is same (on disk) let us keep only one DOM object and reuse it for every other cores. So we can keep a cache at the CoreContainer level .
We save file reading , XML parsing and RAM in one go
The only challenge here is that it is we currently substitute core properties at read time. We will have to postpone this to consumption time. So whenever we read the values from the DOM the values can be substituted and used
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-919) Cache and reuse the SolrConfig
Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Noble Paul updated SOLR-919:
----------------------------
Attachment: SOLR-919.patch
untested patch
> Cache and reuse the SolrConfig
> ------------------------------
>
> Key: SOLR-919
> URL: https://issues.apache.org/jira/browse/SOLR-919
> Project: Solr
> Issue Type: Improvement
> Components: multicore
> Reporter: Noble Paul
> Assignee: Noble Paul
> Fix For: 1.5
>
> Attachments: SOLR-919.patch
>
>
> If there are 1000's of cores the no:of times we need to load and parse the solrconfig.xml is going to be very expensive. It is desirable to just create one instance of SolrConfig object and re-use it across cores
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-919) Cache and reuse the SolrConfig
Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Noble Paul updated SOLR-919:
----------------------------
Description:
If there are 1000's of cores the no:of times we need to load and parse the solrconfig.xml is going to be very expensive. It is desirable to just create one instance of SolrConfig object and re-use it across cores
was:
If there are 1000's of cores the no:of times we need to load and parse the solrconfig.xml is going to be very expensive. In such a case we may mostly have same solrconfig.xml with some core properties embedded
The solution is , if the location of the xml file is same (on disk) let us keep only one DOM object and reuse it for every other cores. So we can keep a cache at the CoreContainer level .
We save file reading , XML parsing and RAM in one go
The only challenge here is that it is we currently substitute core properties at read time. We will have to postpone this to consumption time. So whenever we read the values from the DOM the values can be substituted and used
Fix Version/s: 1.5
Assignee: Noble Paul
Summary: Cache and reuse the SolrConfig (was: Cache and reuse the DOM object of solrconfig.xml)
> Cache and reuse the SolrConfig
> ------------------------------
>
> Key: SOLR-919
> URL: https://issues.apache.org/jira/browse/SOLR-919
> Project: Solr
> Issue Type: Improvement
> Reporter: Noble Paul
> Assignee: Noble Paul
> Fix For: 1.5
>
>
> If there are 1000's of cores the no:of times we need to load and parse the solrconfig.xml is going to be very expensive. It is desirable to just create one instance of SolrConfig object and re-use it across cores
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.