lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Walter Underwood <wun...@wunderwood.org>
Subject Re: How real-time are Soir/Lucene queries?
Date Fri, 21 May 2010 16:08:20 GMT
I chose it, and it doesn't look like they've replaced it in the eight months since I left.

At the time, I was the entire search engineering department, so it was me.

wunder

On May 21, 2010, at 8:49 AM, Dennis Gearon wrote:

> Did your successor choose Solr? I seem to have read an article or seen a 'mobcast' whre
the Search Engine Guy (SEG) @ Netflix used Solr. (Or, maybe ite as another video chain)
> 
> Dennis Gearon
> 
> Signature Warning
> ----------------
> EARTH has a Right To Life,
>  otherwise we all die.
> 
> Read 'Hot, Flat, and Crowded'
> Laugh at http://www.yert.com/film.php
> 
> 
> --- On Thu, 5/20/10, Walter Underwood <wunder@wunderwood.org> wrote:
> 
>> From: Walter Underwood <wunder@wunderwood.org>
>> Subject: Re: How real-time are Soir/Lucene queries?
>> To: solr-user@lucene.apache.org
>> Date: Thursday, May 20, 2010, 10:12 PM
>> Solr is a very good engine, but it is
>> not real-time. You can turn off the caches and reduce the
>> delays, but it is fundamentally not real-time.
>> 
>> I work at MarkLogic, and we have a real-time transactional
>> search engine (and respository). If you are curious, contact
>> me directly.
>> 
>> I do like Solr for lots of applications -- I chose it when
>> I was at Netflix.
>> 
>> wunder
>> 
>> On May 20, 2010, at 7:22 PM, Thomas J. Buhr wrote:
>> 
>>> Hello Soir,
>>> 
>>> Soir looks like an excellent API and its nice to have
>> a tutorial that makes it easy to discover the basics of what
>> Soir does, I'm impressed. I can see plenty of potential uses
>> of Soir/Lucene and I'm interested now in just how real-time
>> the queries made to an index can be?
>>> 
>>> For example, in my application I have time ordered
>> data being processed by a paint method in real-time. Each
>> piece of data is identified and its associated renderer is
>> invoked. The Java2D renderer would then lookup any layout
>> and style values it requires to render the current data it
>> has received from the layout and style indexes. What I'm
>> wondering is if this lookup which would be a Lucene search
>> will be fast enough?
>>> 
>>> Would it be best to make Lucene queries for the
>> relevant layout and style values required by the renderers
>> ahead of rendering time and have the query results placed
>> into the most performant collection (map/array) so renderer
>> lookup would be as fast as possible? Or can Lucene handle
>> many individual lookup queries fast enough so rendering is
>> quick?
>>> 
>>> Best regards from Canada,
>>> 
>>> Thom
>>> 
>> 
>> 
>> 
>> 
>> 
>> 

--
Walter Underwood
Venture ASM, Troop 14, Palo Alto




Mime
View raw message