Re: Performance with multi index

2005-06-17 Thread Volodymyr Bychkoviak
Each time you close indexWriter ram cached documents are flushed to disk. In case you open and close it per document many one-document segments are created on disk. minMergeDocs sets number of documents that are cached in ram. JM Tinghir wrote: do you keep your indexWriter open all the time

Re: Performance with multi index

2005-06-17 Thread JM Tinghir
> do you keep your indexWriter open all the time during process? I think that might be the real cause. And as it reopen it all the time, the mergeFactor isn't used at all I guess... I'll try to modify that. Thanks. Jean-Marie Tinghir -

Re: Performance with multi index

2005-06-16 Thread Volodymyr Bychkoviak
can you measure "pure" index creation time (without creating XMLs) and one more question: do you keep your indexWriter open all the time during process? JM Tinghir wrote: Well, it just took 145 minutes to index 2670 files (450 MB) in one index (29 MB). It only took 33 minutes when I did it int

Re: Performance with multi index

2005-06-16 Thread Chris Collins
I contest to the value of increasing the minMergeDocs.it directly effects how much IO gets performed in indexing. Splitting it into multiple indices (if you want to pay the price of complexity), may well increase your throughput. Assuming you are not utilizing all of the resources the sys

Re: Performance with multi index

2005-06-16 Thread Volodymyr Bychkoviak
my previous message lost somewhere :( reposting can you measure "pure" index creation time (without creating XMLs) and one more question: do you keep your indexWriter open all the time during process? best way to determine bottlenecks is profiling :) regards, Volodymyr Bychkoviak JM Tinghir w

Re: Performance with multi index

2005-06-16 Thread Paul . Illingworth
lease respond to Re: Performance with multi index [EMAIL PROTECTED]

Re: Performance with multi index

2005-06-16 Thread JM Tinghir
> Well, it just took 145 minutes to index 2670 files (450 MB) in one > index (29 MB). > It only took 33 minutes when I did it into ~10 indexes (global size of 32 MB). Forgot to add, that it does not only indexes files, it also creates XML documents. So don't worry if takes 30 minutes to index 450

Re: Performance with multi index

2005-06-16 Thread Volodymyr Bychkoviak
JM Tinghir wrote: Could you qualify a bit more about what is slow? Well, it just took 145 minutes to index 2670 files (450 MB) in one index (29 MB). It only took 33 minutes when I did it into ~10 indexes (global size of 32 MB). I think it took so much time, because it's merged too

Re: Performance with multi index

2005-06-16 Thread JM Tinghir
> Could you qualify a bit more about what is slow? Well, it just took 145 minutes to index 2670 files (450 MB) in one index (29 MB). It only took 33 minutes when I did it into ~10 indexes (global size of 32 MB). > Perhaps you need to optimize the index? Perhaps, never tried it... JM --

Re: Performance with multi index

2005-06-16 Thread Erik Hatcher
On Jun 16, 2005, at 4:08 AM, JM Tinghir wrote: I have a 25 Mb index and was wondering if it would be better to divide it in about 10 indexes and search in it with MutliSearcher. Would searching be faster this way? The indexing would be faster I guess, as it is getting slower and slower while ind

Performance with multi index

2005-06-16 Thread JM Tinghir
Hi, I have a 25 Mb index and was wondering if it would be better to divide it in about 10 indexes and search in it with MutliSearcher. Would searching be faster this way? The indexing would be faster I guess, as it is getting slower and slower while indexes get bigger. But searching? Jean-Marie