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

Ryan McKinley edited comment on SOLR-272 at 6/24/07 3:39 PM:
-------------------------------------------------------------

Running a test that creates 'n' docs each with an id,name, and  a few subjects, 
the results are:

[100000] SolrInputDocument:          1828
[100000] LuceneInputDocument:    2499
[100000] DocumentBuilder:              1746
[1000000] SolrInputDocument:        14162
[1000000] LuceneInputDocument:  19764
[1000000] DocumentBuilder:            17127

(running on JDK 1.6 core 2 duo 2.3ghz)





 was:
Running a test that creates 'n' docs each with an id,name, and  a few subjects, 
the results are:

[100000] SolrInputDocument:    1841
[100000] LuceneInputDocument:  4258
[100000] DocumentBuilder:      5969
[1000000] SolrInputDocument:    14727
[1000000] LuceneInputDocument:  34369
[1000000] DocumentBuilder:      51604

(running on JDK 1.6 core 2 duo 2.3ghz)

Surprisingly it looks like:

SolrInputDocument -- fastest
LuceneInputDocument - ~2x slower
DocumentBuilder - ~3x slower

I'm sure the documents I'm building aren't a good distribution of what random 
documents would look like - BUT, the other style documents (copy fields, things 
with default values, etc) are handled more easily in the already winning 
SolrInputDocument...



> SolrDocument performance testing
> --------------------------------
>
>                 Key: SOLR-272
>                 URL: https://issues.apache.org/jira/browse/SOLR-272
>             Project: Solr
>          Issue Type: Test
>    Affects Versions: 1.3
>            Reporter: Ryan McKinley
>         Attachments: SOLR-272-SolrDocumentPerformanceTesting.patch, 
> SOLR-272-SolrDocumentPerformanceTesting.patch
>
>
> In 1.3, we added SolrInputDocument -- a temporary class to hold document 
> information.  There is concern that this may be less then ideal 
> performance-wise.
> To settle some concerns (mine included) I want to compare a few SolrDocument 
> implementations to make sure we are not doing something crazy.
> I implemented a LuceneInputDocument subclass of SolrInputDocument that stores 
> its values directly in Lucene Document (rather then a Map<String,Collection>).
> This is a quick test comparing:
> 1. Building documents with SolrInputDocument 
> 2. Building documents with LuceneInputDocument (same interface writing 
> directly to Document)
> 3. using DocumentBuilder (solr 1.2, solr 1.1)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to