Yes, when people talk about NRT search they refer to 'add to view lag'. In a typical Solr master-slave setup this is dominated by waiting for replication, doing the replication, and then warming up.
If your problem is indexing speed then that's a separate story that I think you'll find answers to on http://search-lucene.com/ or if you can't find them we can repeat :) Otis ---- Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem search :: http://search-lucene.com/ ----- Original Message ---- > From: Jack Repenning <jrepenn...@collab.net> > To: solr-user@lucene.apache.org > Sent: Fri, June 3, 2011 2:10:27 PM > Subject: Re: Strategy --> Frequent updates in our application > > On Jun 2, 2011, at 8:29 PM, Naveen Gupta wrote: > > > and what about NRT, is it fine to apply in this case of scenario > > Is NRT really what's wanted here? I'm asking the experts, as I have a >situation not too different from the b.p. > > It appears to me (from the dox) that NRT makes a difference in the lag > between >a document being added and it being available in searches. But the BP really >sounds to me like a concern over documents-added-per-second. Does the >RankingAlgorithm form of NRT improve the docs-added-per-second performance? > > My add-to-view limits aren't really threatened by Solr performance today; >something like 30 seconds is just fine. But I am feeling close enough to the >documents-per-second boundary that I'm pondering measures like master/slave. >If >NRT only improvs add-to-view lag, I'm not overly interested, but if it can >improve add throughput, I'm all over it ;-) > > -==- > Jack Repenning > Technologist > Codesion Business Unit > CollabNet, Inc. > 8000 Marina Boulevard, Suite 600 > Brisbane, California 94005 > office: +1 650.228.2562 > twitter: http://twitter.com/jrep > > > > > > > > > >
