AW: Lucene 2.9 and 3.0: Optimized index is thrice as large as the not optimized index

2010-01-11 Thread Yuliya Palchaninava
otherwise the norms will turn themselves back > on when segments merge together. > > Mike > > On Fri, Jan 8, 2010 at 7:55 AM, Yuliya Palchaninava > wrote: > > Thanks Michael. > > > > You are probably wright. > > > > Not optimized size is 4.1G, optimi

AW: Lucene 2.9 and 3.0: Optimized index is thrice as large as the not optimized index

2010-01-08 Thread Yuliya Palchaninava
wise the norms will turn themselves back > on when segments merge together. > > Mike > > On Fri, Jan 8, 2010 at 7:55 AM, Yuliya Palchaninava > wrote: > > Thanks Michael. > > > > You are probably wright. > > > > Not optimized size is 4.1G, optimized inde

AW: Lucene 2.9 and 3.0: Optimized index is thrice as large as the not optimized index

2010-01-08 Thread Yuliya Palchaninava
stored sparsely). > > But: what actual sizes are we talking about? > > Mike > > On Thu, Jan 7, 2010 at 11:50 AM, Yuliya Palchaninava > wrote: > > Otis, > > > > thanks for the answer. > > > > Unfortunatelly the index *directory* remains larger

AW: Lucene 2.9 and 3.0: Optimized index is thrice as large as the not optimized index

2010-01-07 Thread Yuliya Palchaninava
ematext.com/ -- Solr - Lucene - Nutch > > > > - Original Message > > From: Yuliya Palchaninava > > To: "java-user@lucene.apache.org" > > Sent: Thu, January 7, 2010 11:23:08 AM > > Subject: Lucene 2.9 and 3.0: Optimized index is thrice as &g

Lucene 2.9 and 3.0: Optimized index is thrice as large as the not optimized index

2010-01-07 Thread Yuliya Palchaninava
Hi, According to the api documentation: "In general, once the optimize completes, the total size of the index will be less than the size of the starting index. It could be quite a bit smaller (if there were many pending deletes) or just slightly smaller". In our case the index becomes not small