Thanks for your replies! Is there no way to ensure consistency on the disk with 2.3.2?
This is a little off-topic, but is it worth upgrading to 2.4 right now if I've got a very stable system already implemented with 2.3.2? I don't really want to introduce oddities because I'm using an "unfinished" version of Lucene. Is there a rough date for 2.4's release? I poked around the website and couldn't find one. Thanks, Matt Michael McCandless-2 wrote: > > > mattspitz wrote: > >> Are the index files synced on writer.close()? > > No, they aren't. Not until 2.4 (trunk). > >> Thank you so much for your help. I think the seek time is the issue, >> especially considering the high merge factor and the fact that the >> segments >> are scattered all over the disk. > > You're welcome! I agree: optimizing seek time seems likely to be the > biggest win. > >> Will a faster disk cache access affect the optimization and >> merging? I >> don't really have a sense for what of the segments are kept in >> memory during >> a merge. It doesn't make sense to me that Lucene would pull all of >> the >> segments into memory to merge them, but I don't really know how. > > Segments aren't kept in memory during merging... it's more like a > cursor that sweeps through each of the files for the 50 segments being > merged. Lucene does buffer its reads, so we read a chunk into RAM and > then pull bits off that chunk. And the OS does readahead. But > otherwise it's all on disk and we make a single sweep through each of > the segments to be merged. > > So I wouldn't expect the disk cache's performance to impact Lucene, > during merging or flushing. > > Mike > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Appropriate-disk-optimization-for-large-index--tp19009580p19040324.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
