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

David Smiley commented on SOLR-12233:
-------------------------------------

Here's a patch, updated to master, which meant adding FilterQParserPlugin.
I'm running the test stuite / precommit and will commit if it checks out.  My 
tentative CHANGES.txt will be as follows:

(Optimizations)
* SOLR-12233: QParserPlugin's built-in static qparser registry now holds actual 
QParserPlugin instances instead of class references. This is consistent with 
other plugin registries and allows a SolrCore to load faster.  (Jeff Miller, 
David Smiley)

> QParserPlugin maintains a list of classes recreated every time a Solrcore 
> object is created
> -------------------------------------------------------------------------------------------
>
>                 Key: SOLR-12233
>                 URL: https://issues.apache.org/jira/browse/SOLR-12233
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 7.1.1
>            Reporter: Jeff Miller
>            Assignee: David Smiley
>            Priority: Minor
>         Attachments: SOLR-12233.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> QParserPlugin maintains a static map of Class Names to Class objects and 
> everytime we create a SolrCore object this causes a lot of overhead doing 
> classloader lookups.  Our system runs a lot of cores and the classloader gets 
> bogged down when a lot of threads are creating solrcore objects.  
> There's no need to create these objects every time, similar classes such as 
> TransformerFactory store the object one time and reference it over and over 
> again



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to