Hello,
We've created a log management system using lucene 4.3. Each log has about
10 fields and all of them are stored.
We store each hour of the logs in a separate folder so when someone runs a
query only the folders specified in the time frame are searched.
The indexes are loaded using the mmap
:59pm
To: java-user@lucene.apache.org
Subject: Re: Lucene performance issues..
On Sonntag, 27. Juli 2008, Mazhar Lateef wrote:
We have also tried upgrading the lucene version to 2.3 in hope to
improve performance but the results were quite the opposite. but
from my
research on the internet the Lucene
On Sun, 2008-07-27 at 21:38 +0100, Mazhar Lateef wrote:
> * email searching
> o We are creating very large indexes for emails we are
> processing, the size is upto +150GB for indexes only (not
> including data content), this we thought would improve
> search
o change for a while.
>
>
> -Original Message-
> From: "Daniel Naber" <[EMAIL PROTECTED]>
> Sent: Sunday, July 27, 2008 4:59pm
> To: java-user@lucene.apache.org
> Subject: Re: Lucene performance issues..
>
> On Sonntag, 27. Juli 2008, Mazhar Lateef wrote:
nt: Sunday, July 27, 2008 4:59pm
To: java-user@lucene.apache.org
Subject: Re: Lucene performance issues..
On Sonntag, 27. Juli 2008, Mazhar Lateef wrote:
> We have also tried upgrading the lucene version to 2.3 in hope to
> improve performance but the results were quite the opposite. but fro
On Sonntag, 27. Juli 2008, Mazhar Lateef wrote:
> We have also tried upgrading the lucene version to 2.3 in hope to
> improve performance but the results were quite the opposite. but from my
> research on the internet the Lucene version 2.3 is much faster and
> better so why are we seeing such inc
Hi,
we have a system to archive mails and are facing some issues that we are
having with search and indexing performance, the following is what we
are currently facing challenges with, we are currently using lucene
version 2.2 the platform is SLES10.1 and the application is written in
Java.
Your grinder output seems to indicate clearly that your bottleneck is
in your database code, not in lucene. It seems that the threads are
all blocked trying to get a connection from a connection pool. Maybe
you're leaking connections, or maybe you need to increase the size of
the pool.
On 1/3/
t;
To: java-user@lucene.apache.org
Sent: Thursday, January 3, 2008 9:40:53 PM
Subject: lucene performance issues
Folks,
We're running into some performance bottle neck issues while running
lucene search against our indices (approx 1.5 GB in size after
optimization), and the search query seems to block
Folks,
We're running into some performance bottle neck issues while running lucene
search against our indices (approx 1.5 GB in size after optimization), and
the search query seems to block on a sychronized read as follows. Obviously we
can upgrade to the latest as a first step. When Tomcat r
ical RAM on the box.
-Kevin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 28, 2006 12:47 PM
To: java-user@lucene.apache.org
Subject: Commercial vendors monitoring this ML? was: Lucene Performance
Issues
Weird, I was just about to comment on the
ue" in the business
referring them to me.
Jeff Wang
diCarta, Inc.
-Original Message-
From: Otis Gospodnetic [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 28, 2006 8:39 AM
To: java-user@lucene.apache.org
Subject: Re: Lucene Performance Issues
Hi Thomas,
Sound like FUD to me. No concre
I'd rather
be developing with open source tools but the project manager thought it good
to ask around. Thanks again and will get some benchmarks that will mean more
than guesswork.
--
View this message in context:
http://www.nabble.com/Lucene-Performance-Issues-t1354811.html#a3633569
Sent
suggest you try both and see which one suits
your needs.
Otis
- Original Message
From: thomasg <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Tuesday, March 28, 2006 5:06:54 AM
Subject: Lucene Performance Issues
Hi, we are currently intending to implement a document
thomasg wrote:
Hi, we are currently intending to implement a document storage / search tool
using Jackrabbit and Lucene. We have been approached by a commercial search
and indexing organisation called ISYS who are suggesting the following
problems with using Lucene. We do have a requirement to st
thomasg wrote:
1) By default, Lucene only indexes the first 10,000 words from each
document. When increasing this default out-of-memory errors can occur. This
implies that documents, or large sections thereof, are loaded into memory.
ISYS has a very small memory footprint which is not affected by
ge in context:
http://www.nabble.com/Lucene-Performance-Issues-t1354811.html#a3626992
Sent from the Lucene - Java Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
17 matches
Mail list logo
