John Wang wrote:
Is the operation IndexSearcher.search I/O or CPU bound if I am doing
100's of searches on the same query?
CPU bound.
Doug
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTE
Thanks Doug! You are right, by adding a Thread.sleep() helped greatly.
Mysteries of Java...
Another Java threading question.
With 1 thread, iterations of 100 searches, it took about 850 ms.
by adding a Thread.sleep(10) in the loop. It is taking about 2200 ms.
So there is 2200 - 1850 = 350 ms una
Is the operation IndexSearcher.search I/O or CPU bound if I am doing
100's of searches on the same query?
Thanks
-John
On Thu, 06 Jan 2005 10:31:49 -0800, Doug Cutting <[EMAIL PROTECTED]> wrote:
> John Wang wrote:
> > 1 thread: 445 ms.
> > 2 threads: 870 ms.
> > 5 threads: 2200 ms.
> >
> > Pret
John Wang wrote:
1 thread: 445 ms.
2 threads: 870 ms.
5 threads: 2200 ms.
Pretty much the same numbers you'd get if you are running them sequentially.
Any ideas? Am I doing something wrong?
If you're performing compute-bound work on a single-processor machine
then threading should give you no bett
I actually ran a few tests. But seeing similar behaviors.
After removing all the possible variations, this is what I used:
1 Index, doccount is 15,000.
Using FSDirectory, e.g. new IndexSearcher(String path), by default I
think it uses FSDirectory.
each thread is doing 100 iterations of search, e
Hi,
I have a question.
How big (in size and documents) is your index ?
How many indexes do you search ?
Thanks,
Mariella
At 10:54 AM 1/5/2005 -0800, you wrote:
Hi folks:
We are trying to measure thru-put lucene in a multi-threaded
environment.
This is what we found:
1 thread, search
: This is what we found:
:
: 1 thread, search takes 20 ms.
:
: 2 threads, search takes 40 ms.
:
: 5 threads, search takes 100 ms.
how big is your index? What are the term frequencies like in your index?
how many differnt queries did you try? what was the structure of your
qu
Hi folks:
We are trying to measure thru-put lucene in a multi-threaded environment.
This is what we found:
1 thread, search takes 20 ms.
2 threads, search takes 40 ms.
5 threads, search takes 100 ms.
Seems like under a multi-threaded scenario, thru-put isn't go
