Very grateful for Toke Eskildsen of attention my questions.
> Date: Fri, 13 Jun 2008 08:59:27 +0200> From: [EMAIL PROTECTED]> Subject: RE:
> The performance of lucene searching(web entironment) test> To:
> java-user@lucene.apache.org> > On Wed, 2008-06-11 at 18:56 +0800
On Wed, 2008-06-11 at 18:56 +0800, lutan wrote:
> Yes ,I have test again with same entironment but to use singleton
> IndexSearcher.the performance has increased. there 100 concurrent
> user request use different keyword ,and get 60 TPS(2 TPS before).
> and now the bottleneck seem to be CPU,and
Thanks for you replay!> Date: Wed, 11 Jun 2008 09:19:46 +0200> From: [EMAIL
PROTECTED]> Subject: RE: The performance of lucene searching(web entironment)
test> To: java-user@lucene.apache.org> > On Wed, 2008-06-11 at 00:17 +0800,
lutan wrote:> > In my test case , I st
On Wed, 2008-06-11 at 00:17 +0800, lutan wrote:
> In my test case , I start loadrunner jsut test for 5 minute,and the response
> growth slowly.the TPS(transactions per second) seems stoped at 10 finally.
That's without reusing the searcher, right? In that case the increased
rate must be attribute
index
size..?
> Date: Tue, 10 Jun 2008 16:34:17 +0200> From: [EMAIL PROTECTED]> Subject: Re:
> The performance of lucene searching(web entironment) test> To:
> java-user@lucene.apache.org> > On Tue, 2008-06-10 at 21:11 +0800, lutan
> wrote:> > [A lot of text wit
On Tue, 2008-06-10 at 21:11 +0800, lutan wrote:
> [A lot of text with code and no newlines, making it very hard to read]
In your test you're reusing the searcher. For each search your program
performs, you will see faster response times, until the searcher is
fully warmed.
If your production-syst
I have recently done some tests on lucene. I do not know whether the test
results normal. hd entironment:Intel(R) Xeon(R) CPU 5110 @ 1.60GHz4GB ram sw
entironment:centOS4.6+sun jdk 1.5+jboss+lucene2.3.2+je-analysis(a chinese
analysis)there are 10 million+ documents which total about 3GB test
