I have a use case where I build my index only occasionally and am willing to pay the cost to build a read-only index that occupies as small a memory footprint as possible and also remains efficient for posting list traversal. I.e., I will not be making any changes at all once it is built.
1. What is the best strategy to build this index - is there the equivalent of an "optimize()" method (it seems to be gone now, is there a specific codec I can use, etc. 2. Do we get any better read (posting list traversal essentially) performance by doing this (as opposed to using a mutable index)? Thanks, Sriram.
