You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Darren Govoni <da...@ontrenet.com> on 2012/07/22 23:03:33 UTC
Re: [Announce] Solr 4.0-ALPHA with RankingAlgorithm 1.4.4 with
Realtime NRT available for download
What exactly is "Realtime NRT" (Near Real Time)?
On Sun, 2012-07-22 at 14:07 -0700, Nagendra Nagarajayya wrote:
> Hi!
>
> I am very excited to announce the availability of Solr 4.0-ALPHA with
> RankingAlgorithm 1.4.4 with Realtime NRT. The Realtime NRT
> implementation now supports both RankingAlgorithm and Lucene. Realtime
> NRT is a high performance and more granular NRT implementation as to
> soft commit. The update performance is about 70,000 documents / sec*.
> You can also scale up to 2 billion documents* in a single core, and
> query half a billion documents index in ms**.
>
> RankingAlgorithm 1.4.4 supports the entire Lucene Query Syntax, ± and/or
> boolean queries and is compatible with the new Lucene 4.0-ALPHA api.
>
> You can get more information about Solr 4.0-ALPHA with RankingAlgorithm
> 1.4.4 Realtime performance from here:
> http://solr-ra.tgels.org/wiki/en/Near_Real_Time_Search_ver_4.x
>
> You can download Solr 4.0-ALPHA with RankingAlgorithm 1.4.4 from here:
> http://solr-ra.tgels.org
>
> Please download and give the new version a try.
>
> Regards,
>
> Nagendra Nagarajayya
> http://solr-ra.tgels.org
> http://rankingalgorithm.tgels.org
>
> * performance seen at a user installation of Solr 4.0 with
> RankingAlgorithm 1.4.3
> ** performance seen when using the age feature
>
Re: [Announce] Solr 4.0-ALPHA with RankingAlgorithm 1.4.4 with Realtime
NRT available for download
Posted by Nagendra Nagarajayya <nn...@transaxtions.com>.
Realtime NRT is a NRT implementation available for Solr 1.4.1 to Solr
4.0. To enable NRT it makes available a NRTIndexReader to the
IndexSearcher for searching the index. It does not close the
SolrIndexSearcher which is a very heavy object with caches, etc. to do
this. Since the Searcher is never closed it always uses the most recent
NRTIndexReader for searching and you get a pipe that is always filled
with new updated documents. The code changes are to handle this dynamic
pipe that may always have something new as in a realtime system.
Realtime NRT is different from soft commit as it does not close the
SolrIndexSearcher object every 1000 secs, invalidating the caches, etc.
SolrIndexSearcher is a very heavy object, ref. counted with caches, etc.
Closing it every time may turn out to be expensive.
I am contributing Realtime NRT to Solr 4.0 and am working on making
available a patch, etc.
Regards,
Nagendra Nagarajayya
http://solr-ra.tgels.org
http://rankingalgorithm.tgels.org
On 7/22/2012 2:03 PM, Darren Govoni wrote:
> What exactly is "Realtime NRT" (Near Real Time)?
>
> On Sun, 2012-07-22 at 14:07 -0700, Nagendra Nagarajayya wrote:
>
>> Hi!
>>
>> I am very excited to announce the availability of Solr 4.0-ALPHA with
>> RankingAlgorithm 1.4.4 with Realtime NRT. The Realtime NRT
>> implementation now supports both RankingAlgorithm and Lucene. Realtime
>> NRT is a high performance and more granular NRT implementation as to
>> soft commit. The update performance is about 70,000 documents / sec*.
>> You can also scale up to 2 billion documents* in a single core, and
>> query half a billion documents index in ms**.
>>
>> RankingAlgorithm 1.4.4 supports the entire Lucene Query Syntax, ± and/or
>> boolean queries and is compatible with the new Lucene 4.0-ALPHA api.
>>
>> You can get more information about Solr 4.0-ALPHA with RankingAlgorithm
>> 1.4.4 Realtime performance from here:
>> http://solr-ra.tgels.org/wiki/en/Near_Real_Time_Search_ver_4.x
>>
>> You can download Solr 4.0-ALPHA with RankingAlgorithm 1.4.4 from here:
>> http://solr-ra.tgels.org
>>
>> Please download and give the new version a try.
>>
>> Regards,
>>
>> Nagendra Nagarajayya
>> http://solr-ra.tgels.org
>> http://rankingalgorithm.tgels.org
>>
>> * performance seen at a user installation of Solr 4.0 with
>> RankingAlgorithm 1.4.3
>> ** performance seen when using the age feature
>>
>