Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-272

SolrDocument performance testing

    XMLWordPrintableJSON

    Details

    • Type: Test
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.3
    • Fix Version/s: 1.3
    • Component/s: None
    • Labels:
      None

      Description

      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)

        Attachments

        1. SOLR-272-SolrDocumentPerformanceTesting.patch
          19 kB
          Ryan McKinley
        2. SOLR-272-SolrDocumentPerformanceTesting.patch
          19 kB
          Ryan McKinley
        3. SolrDocumentPerformanceTester.java
          3 kB
          Yonik Seeley
        4. SolrDocumentPerformanceTester.java
          3 kB
          Ryan McKinley
        5. SolrInputDoc.patch
          15 kB
          Ryan McKinley
        6. SolrInputDoc.patch
          15 kB
          Yonik Seeley

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ryantxu Ryan McKinley
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: