Your code should probably be pro-active, tracking the number of terms it is adding with each document to the index so it can estimate how big the index is growing rather than simply checking the sizes of the index files. Certainly you won't want to run optimize until you've completed preparing the index for each DVD. But you certainly will want to run optimize before writing the DVD so the index opens and searches faster.
-- Neal -----Original Message----- From: Jerry Camel [mailto:rlrc...@msn.com] Sent: Tuesday, October 27, 2009 11:17 AM To: lucene-net-user@incubator.apache.org Subject: Re: Monitoring Index Size It's not an inaccuracy that's the issue. It's that I keep getting exceptions thrown during the process. I was trying to get an approximate size without closing the index. If I've got 14,000 documents to index, closing the index and optimizing after each document is a lot of overhead. But, I fear, that may be my only option... -------------------------------------------------- From: "Franklin Simmons" <fsimm...@sccmediaserver.com> Sent: Tuesday, October 27, 2009 12:11 PM To: <lucene-net-user@incubator.apache.org> Subject: RE: Monitoring Index Size > Maybe one reason you are not getting an accurate account of the index size > is IndexWriter buffering (MaxBufferedDocs). IndexWriter.Flush and > IndexWriter.Optimize should prove useful in that regard. IndexWriter's > code documentation covers buffering, commits etc in fair detail. > > > -----Original Message----- > From: Jerry Camel [mailto:rlrc...@msn.com] > Sent: Tuesday, October 27, 2009 11:26 AM > To: lucene-net-user@incubator.apache.org > Subject: Re: Monitoring Index Size > > Hello, hello... Is this thing on? Can someone please acknowledge that my > messages are coming through to the group? I've sent several questions > over > the last few weeks and nary a response. Thanks. > > J > > -------------------------------------------------- > From: "Jerry Camel" <rlrc...@msn.com> > Sent: Monday, October 26, 2009 2:48 PM > To: <lucene-net-user@incubator.apache.org> > Subject: Monitoring Index Size > >> I've got a project where I need to create DVD sized collections of >> indexed >> data. Each disc will contain and index folder and a data folder. >> Contents should be obvious. My question is how can I monitor the index >> size as I'm adding data so I can determine when the size of the data plus >> the size of the index crosses a pre-determined threshold and I can close >> out the disc and move on to the next? >> >> At the moment I'm looping through the index folder and just sizing the >> files. But it appears that Lucene is processing, as well, and sometimes >> I >> try to get the size of a file that is no longer there. >> >> Any advice on how to approach this without having to completely close the >> index after each document? >> >> Thanks. >> >> J > >
