Chris Lamprecht wrote:
I've done exactly what you describe, using N threads where N is the
number of processors on the machine, plus one more thread that writes
to the file system index (since that is I/O-bound anyway). Since most
of the CPU time is tokenizing/stemming/etc, the method works well.
Hi Sodel,
You could use a single queue, where one thread pulls things off the
queue and any number of threads put things on the queue. You can
index say 1000 documents each to RAMDirectories in multiple threads,
then enqueue the RAMDirectories. When the queue reaches a certain
size, the single t
individual
RAMDirectories.
-Original Message-
From: Sodel Vazquez-Reyes
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 03, 2005 11:12 AM
To: lucene-user@jakarta.apache.org
Subject: Indexing in multi-threaded environment
Hi,
I am starting my application in multi-threaded environment,
could
]
Sent: Tue 3-5-2005 20:11
To: lucene-user@jakarta.apache.org
Subject: Indexing in multi-threaded environment
Hi,
I am starting my application in multi-threaded environment,
could somebody show me any examples with serialize calls to the
IndexWriter.addDocument(Document)?
because my idea is to use
Hi,
I am starting my application in multi-threaded environment,
could somebody show me any examples with serialize calls to the
IndexWriter.addDocument(Document)?
because my idea is to use RAMDirectory based in parallel, one in each
thread, and merges them into a single index on the disk using
Ind
