Hello, Yes, that is how optimize works - copies all existing index segments into one unified index segment, thus optimizing it.
see hit #1: http://www.lucenebook.com/search?query=optimize+disk+space However, three times the space sounds a bit too much, or I make a mistake in the book. :) You said you end up with 3 files - .cfs is one of them, right? Otis --- "Kauler, Leto S" <[EMAIL PROTECTED]> wrote: > > Just a quick question: after writing an index and then calling > optimize(), is it normal for the index to expand to about three times > the size before finally compressing? > > In our case the optimise grinds the disk, expanding the index into > many > files of about 145MB total, before compressing down to three files of > about 47MB total. That must be a lot of disk activity for the people > with multi-gigabyte indexes! > > Regards, > Leto > > CONFIDENTIALITY NOTICE AND DISCLAIMER > > Information in this transmission is intended only for the person(s) > to whom it is addressed and may contain privileged and/or > confidential information. If you are not the intended recipient, any > disclosure, copying or dissemination of the information is > unauthorised and you should delete/destroy all copies and notify the > sender. No liability is accepted for any unauthorised use of the > information contained in this transmission. > > This disclaimer has been automatically added. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
