[
https://issues.apache.org/jira/browse/SOLR-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-272:
-------------------------------
Attachment: SolrDocumentPerformanceTester.java
Since the LuceneInputDocument is an obvious looser, I removed that from the
test.
I also:
* removed Random from the mix -- makes the tests inconsistent
* test simple and complex docs.
> simple is just the id
> complex is id + name + dynamic field + 10 subjects, the subjects each have
a copyField to 'text'
With this test, the SolrInputDocument wins every time:
[100000] 2043 :: 0.02043 mili/doc :: SolrInputDocument - true
[100000] 2193 :: 0.02193 mili/doc :: DocumentBuilder - true
[1000000] 15815 :: 0.015815 mili/doc :: SolrInputDocument - true
[1000000] 19223 :: 0.019223 mili/doc :: DocumentBuilder - true
[10000000] 6228 :: 0.000623 mili/doc :: SolrInputDocument - false
[10000000] 17263 :: 0.001726 mili/doc :: DocumentBuilder - false
> 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,
> SolrDocumentPerformanceTester.java
>
>
> 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.
