Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of teddyyyy123@gmail.com
 designates 209.85.217.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEY5pxWCXFoFqdCT2Z4KGhRr6ZQGjamSk10ouzY5bYVVqvbKCA@mail.gmail.com>
References: 
 <CAAnh3_8iE902V7Nbj_BJcPpi9DMRvHVjbN_Z1+emxUS9YLth8g@mail.gmail.com>
 <CAFAd71U+tV7CP43yrjFQ9SzeHSXTohJRTZWfRjag94M-NMVMQw@mail.gmail.com>
 <CAFAd71Wa9JiGt1VUy1mDD9EP3Jk9VR2S458P5XbOnUJEG6F7HA@mail.gmail.com>
 <CAEY5pxWCXFoFqdCT2Z4KGhRr6ZQGjamSk10ouzY5bYVVqvbKCA@mail.gmail.com>
From: Yang <teddyyyy123@gmail.com>
Date: Fri, 25 May 2012 17:47:51 -0700
Message-ID: 
 <CAAnh3_-7NZf9h33fNi=RSyFrSM+YaFnS-En0bhTXJHuW0gNY5w@mail.gmail.com>
Subject: Re: lucene (search) performance tuning
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=f46d040891abe6761b04c0e5d629

--f46d040891abe6761b04c0e5d629
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

thanks a lot guys

On Tue, May 22, 2012 at 1:34 AM, Ian Lea <ian.lea@gmail.com> wrote:

> Lots of good tips in
> http://wiki.apache.org/lucene-java/ImproveSearchingSpeed, linked from
> the FAQ.
>
>
> --
> Ian.
>
>
> On Tue, May 22, 2012 at 2:08 AM, Li Li <fancyerii@gmail.com> wrote:
> > something wrong when writing in my android client.
> > if RAMDirectory do not help, i think the bottleneck is cpu. you may try
> to
> > tune jvm but i do not expect much improvement.
> > the best one is splitting your index into 2 or more smaller ones.
> > you can then use solr s distributed searching.
> > if the cpu is not fully used, yuo can do this in one physical machine
> >
> > =E5=9C=A8 2012-5-22 =E4=B8=8A=E5=8D=888:50=EF=BC=8C"Li Li" <fancyerii@g=
mail.com>=E5=86=99=E9=81=93=EF=BC=9A
> >>
> >>
> >> =E5=9C=A8 2012-5-22 =E5=87=8C=E6=99=A84:59=EF=BC=8C"Yang" <teddyyyy123=
@gmail.com>=E5=86=99=E9=81=93=EF=BC=9A
> >>
> >> >
> >> > I'm trying to make my search faster. right now a query like
> >> >
> >> > name:Joe Moe Pizza   address:77 main street  city:San Francisco
> >> >is this a conjunction query or a disjunction query=EF=BC=9F
> >>
> >> > in a index with 20mil such short business descriptions (total size
> > about 3GB) takes about 100--200ms.
> >> >20m is not a small size, how many results for a query in average=EF=
=BC=9F
> >>
> >> > I profiled the query, most time is spent in TermScorer.score(), as i=
s
> > shown by the attached yourkit screenshot.
> >> >that=EF=BC=87s true, for a query, matching and scoring is very time c=
onsuming
> > and cpu intensive. another one is io for reading postings.
> >>
> >> >
> >> >
> >> >
> >> > I tried loading the index onto tmpfs (in-memory block device), and
> also
> > tried RAMDirectory, neither helps much.
> >> >if that is true. it seems that io is not the
> >> > I am reading
> > http://www.cnlp.org/presentations/slides/AdvancedLuceneEU.pdf
> >> > it mentions
> >> > Size
> >> > =E2=80=93 Stopword removal
> >> > =E2=80=93 Stemming
> >> > =E2=80=A2 Lucene has a number of stemmers available
> >> > =E2=80=A2 Light versus Aggressive
> >> > =E2=80=A2 May prevent fine-grained matches in some cases
> >> > =E2=80=93 Not a linear factor (usually) due to index compression
> >> >
> >> > so for "stopword removal", I'm already using the standard analyzer, =
so
> > stop word removal is already included, right?
> >> >
> >> > also generally any other tricks to try for reducing the search
> latency?
> >> >
> >> > Thanks!
> >> > Yang
> >> >
> >> >
> >> > --------------------------------------------------------------------=
-
> >> > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> >> > For additional commands, e-mail: java-user-help@lucene.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

--f46d040891abe6761b04c0e5d629--