matext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
- Original Message
> From: Salman Akram
> To: solr-user@lucene.apache.org
> Sent: Mon, February 7, 2011 2:49:44 AM
> Subject: Re: Performance optimization of Proximity/Wildcard searches
>
.org
> > Sent: Sat, February 5, 2011 4:06:54 AM
> > Subject: Re: Performance optimization of Proximity/Wildcard searches
> >
> > Correct me if I am wrong.
> >
> > Commit in index flushes SOLR cache but of course OS cache would still be
> > useful? If a an index i
t; > Otis
> >
> > Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> > Lucene ecosystem search :: http://search-lucene.com/
> >
> >
> >
> > - Original Message
> > > From: Salman Akram
> > > To: solr-user@lucene.apache.o
>
> Otis
>
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Lucene ecosystem search :: http://search-lucene.com/
>
>
>
> - Original Message
> > From: Salman Akram
> > To: solr-user@lucene.apache.org
> > Sent: Fri, February 4, 2011 3:
>
>
>
> - Original Message
> > From: Salman Akram
> > To: solr-user@lucene.apache.org
> > Sent: Fri, February 4, 2011 3:33:41 PM
> > Subject: Re: Performance optimization of Proximity/Wildcard searches
> >
> > I know so we are not really using it fo
.apache.org
> Sent: Fri, February 4, 2011 3:38:55 PM
> Subject: Re: Performance optimization of Proximity/Wildcard searches
>
> Well I assume many people out there would have indexes larger than 100GB and
> I don't think so normally you will have more RAM than 32GB or 64!
>
rom: Salman Akram
> To: solr-user@lucene.apache.org
> Sent: Fri, February 4, 2011 3:33:41 PM
> Subject: Re: Performance optimization of Proximity/Wildcard searches
>
> I know so we are not really using it for regular warm-ups (in any case index
> is updated on hourly basis). Ju
>
>
> - Original Message
> > From: Salman Akram
> > To: solr-user@lucene.apache.org
> > Sent: Tue, January 25, 2011 4:20:34 AM
> > Subject: Performance optimization of Proximity/Wildcard searches
> >
> > Hi,
> >
> > I am facing performance i
t; - Original Message
> > From: Salman Akram
> > To: solr-user@lucene.apache.org; t...@statsbiblioteket.dk
> > Sent: Tue, January 25, 2011 6:32:48 AM
> > Subject: Re: Performance optimization of Proximity/Wildcard searches
> >
> > By warmed index you onl
ne.apache.org
> Sent: Tue, January 25, 2011 4:20:34 AM
> Subject: Performance optimization of Proximity/Wildcard searches
>
> Hi,
>
> I am facing performance issues in three types of queries (and their
> combination). Some of the queries take more than 2-3 mins. Index size
e.apache.org; t...@statsbiblioteket.dk
> Sent: Tue, January 25, 2011 6:32:48 AM
> Subject: Re: Performance optimization of Proximity/Wildcard searches
>
> By warmed index you only mean warming the SOLR cache or OS cache? As I said
> our index is updated every hour so I am not sure h
By warmed index you only mean warming the SOLR cache or OS cache? As I said
our index is updated every hour so I am not sure how much SOLR cache would
be helpful but OS cache should still be helpful, right?
I haven't compared the results with a proper script but from manual testing
here are some o
On Tue, 2011-01-25 at 10:20 +0100, Salman Akram wrote:
> Cache warming is a good option too but the index get updated every hour so
> not sure how much would that help.
What is the time difference between queries with a warmed index and a
cold one? If the warmed index performs satisfactory, then o
Hi,
I am facing performance issues in three types of queries (and their
combination). Some of the queries take more than 2-3 mins. Index size is
around 150GB.
- Wildcard
- Proximity
- Phrases (with common words)
I know CommonGrams and Stop words are a good way to resolve such issues bu
14 matches
Mail list logo
