lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pisarev, Vitaliy" <>
Subject Solr perfromance with commitWithin seesm too good to be true. I am afraid I am missing something
Date Wed, 12 Feb 2014 14:52:01 GMT
I am running a very simple performance experiment where I post 2000 documents to my application.
Who in turn persists them to a relational DB and sends them to Solr for indexing (Synchronously,
in the same request).
I am testing 3 use cases:

  1.  No indexing at all - ~45 sec to post 2000 documents
  2.  Indexing included - commit after each add. ~8 minutes (!) to post and index 2000 documents
  3.  Indexing included - commitWithin 1ms ~55 seconds (!) to post and index 2000 documents
The 3rd result does not make any sense, I would expect the behavior to be similar to the one
in point 2. At first I thought that the documents were not really committed but I could actually
see them being added by executing some queries during the experiment (via the solr web UI).
I am worried that I am missing something very big. The code I use for point 2:
SolrInputDocument = // get doc
SolrServer solrConnection = // get connection
Whereas the code for point 3:
SolrInputDocument = // get doc
SolrServer solrConnection = // get connection
solrConnection.add(doc, 1); // According to API documentation I understand there is no need
to explicitly call commit with this API
Is it possible that committing after each add will degrade performance by a factor of 40?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message