Hi,

In our specific implementation this is not really an issue, but I can imagine 
it could impact performance. I guess a new thread could spawned, which takes 
care of any performance issues, thanks for pointing it out. I'll post a message 
when I coded the change.

Regards,

Patrick


-----Original Message-----
From: rswart [mailto:rjsw...@gmail.com] 
Sent: dinsdag 26 mei 2009 16:42
To: solr-user@lucene.apache.org
Subject: RE: Solr statistics of top searches and results returned


If this is is not done in an async way wouldn't this have a serious performance 
impact? 

 

Plaatje, Patrick wrote:
> 
> Hi all,
> 
> I created a script that uses a Solr Search Component, which hooks into 
> the main solr core and catches the searches being done. After this it 
> tokenizes the search and send both the tokenized as well as the 
> original query to another Solr core. I have not written a factory for 
> this, but if required, it shouldn't be so hard to modify the script 
> and code Database support into it.
> 
> You can find the source here:
> 
> http://www.ipros.nl/uploads/Stats-component.zip
> 
> It includes a README, and a schema.xml that should be used.
> 
> Please let me know you're thoughts.
> 
> Best,
> 
> Patrick
> 
> 
> 
>  
> 
> -----Original Message-----
> From: Umar Shah [mailto:u...@wisdomtap.com]
> Sent: vrijdag 22 mei 2009 10:03
> To: solr-user@lucene.apache.org
> Subject: Re: Solr statistics of top searches and results returned
> 
> Hi,
> 
> good feature to have,
> maintaining top N would also require storing all the search queries 
> done so far and keep updating (or atleast in some time window).
> 
> having pluggable persistent storage for all time search queries would 
> be great.
> 
> tell me how can I help?
> 
> -umar
> 
> On Fri, May 22, 2009 at 12:21 PM, Shalin Shekhar Mangar 
> <shalinman...@gmail.com> wrote:
>> On Fri, May 22, 2009 at 3:22 AM, Grant Ingersoll
>> <gsing...@apache.org>wrote:
>>
>>>
>>> I think you will want some type of persistence mechanism otherwise 
>>> you will end up consuming a lot of resources keeping track of all 
>>> the query strings, unless I'm missing something.  Either a Lucene 
>>> index (Solr core) or the option of embedding a DB.  Ideally, it 
>>> would be pluggable such that people could choose their storage mechanism.
>>> Most people do this kind of thing offline via log analysis as logs 
>>> can grow quite large quite quickly.
>>>
>>
>> For a general case, yes. But I was thinking more of a top 'n' queries 
>> as a running statistic.
>>
>> --
>> Regards,
>> Shalin Shekhar Mangar.
>>
> 
> 

--
View this message in context: 
http://www.nabble.com/Solr-statistics-of-top-searches-and-results-returned-tp23621779p23724277.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to