Basically I expect you're falling afoul of a very common misunderstanding; It's not that Solr is slower, it's that the client isn't feeding Solr as fast as it should.
If you profile your Solr server, my suspicion is that you're not driving it very hard. You'll probably see 4 spikes in CPU activity, followed by it doing nothing at all. The spikes are when you actually send the doclist to Solr. Your client is creating a 250K document packet, _then_ transmitting it to Solr, waiting for the response, then creating another packet. While creating a packet, Solr is doing nothing at all, just waiting. You'll get better performance by using ConcurrentUpdateSolrClient and much smaller packets (say 1,000). Give it, say, 10 threads and a queue length of 10 or so. You'll have to experiment for sure. Now, all that said since Solr is wrapping Lucene, since there's some additional overhead because Solr has to parse out the doc and pass it on to Lucene etc, you'll inevitably see some degradation. It shouldn't be as extreme as you're seeing though so I'm pretty sure you'll find your client isn't written to get the best performance out of Solr. In future, please don't link questions to another forum. It makes it less likely that people will actually respond. Best, Erick On Mon, Jun 15, 2015 at 6:52 AM, Alessandro Benedetti <benedetti.ale...@gmail.com> wrote: > Actually I can see a problem in your question… > Lucene and Solr are not competitor technologies. > Solr is a Search Server that internally uses the Lucene library and offers > easy to use configuration and REST API. > Lucene is a library that implements tons of search algorithms and features. > You can see Solr as "best practice for Lucene" implemented server. > It offers out of the box a usable search server with tons of features easy > to use( take a look to the official site to have an idea) . > > On the other hand Lucene is a library, so you can develop with it your > personal Search Server or Search application. > More than performance you should really understand if you want to rewrite a > lot of already implemented search features, or maybe re-use the ones > developer by Lucene gurus. > > Furthermore of course, it depends of the feature you really need for your > application. > > Cheers > > 2015-06-15 13:16 GMT+01:00 Argho Chatterjee < > joy.chatterjee.crazyc...@gmail.com>: > >> Hello Everyone, >> >> I had posted a question on stackoverflow.com after performing a few POCs >> >> My hadrware consist of a single i-3 intel processor (4 CPU as per "dxdiag" >> on run ), 8GB Ram, Laptop machine. >> >> My Question Link : >> >> http://stackoverflow.com/questions/30823314/lucene-vs-solr-indexning-speed-for-sampe-data >> >> but no one could solve it as of now.. >> I hope the question I posted is undertandable. >> >> Please if anyone could help me out with the indexing speed of Solr (way >> slower) vs Lucene (way faster).. >> >> I am trying to build a module for real time indexing and querying, and the >> traffic is high, POC pass with Lucene for handling High Traffic for >> Indexing, for Solr It is not able to do so.. >> >> Again My Machine Spec : >> HP, intel core i3, 8GB ram, TB HDD. >> >> Please let me know if there is a problem with Solr or am I doing anything >> wrong. >> >> Thanks >> Argho >> > > > > -- > -------------------------- > > Benedetti Alessandro > Visiting card : http://about.me/alessandro_benedetti > > "Tyger, tyger burning bright > In the forests of the night, > What immortal hand or eye > Could frame thy fearful symmetry?" > > William Blake - Songs of Experience -1794 England
