: The numbers vary quite a bit though, from 13 docs/s (Burkamp) : to 250 docs/s (Walter) to 1000 docs/s I understand the results also depend : on the doc size and hardware.
It also depends a lot on how much analysis you do of each field ... and that doesn't even begin to get totheissue of what kinds of work you do to gather the data up and format it into XML docs to send to Solr ... i've yet to see an application where Solr is the bottleneck during, typically we set up a producer/consumer model for indexing and the queue is almost allways empty (a few docs might queue up during a segment merge) : I have a question for Erik: you mentioned "single threaded indexer" : (below). I'm not familiar with solr at all and did a search on solr : wiki for "thread" and didn't find anything. Is it so that I can : actually configure solr to be single-threaded and multi-threaded? : : And I'm not sure what you meant by parallelizing the indexer? : Running multiple instances of the indexer, or multiple instances : of solr? i believe what erik was refering to was making the client code you write which gathers up your data and submits it to solr multithreaded ... for most cases a single threaded app that reads docs one at a time from your authoritative data store and sends them to Solr works fine, but if you want to speed things up, unless you find that Solr is your bottleneck, making the process sending the updates multithreaded can probably help. -Hoss
