Thanks for the advice guys... i'm still not entirely clear on what a search causes Lucene to do with respect to warming up/caching portions of the index in memory.
If I warm up lucene using a search for "apple", does Lucene load the entire inverted index into Memory, or just the part of the index that contains the entry for "apple" ? Basically I'd like to make sure that the entire inverted index (or as much as possible) is preloaded into memory, so if I issue a subsequent search for "microsoft", it will be fast. Does Lucene have any mechanism for preloading the inverted index into memory? Also is there a way to figure out what percentage of lucene's data storage is occupied by the inverted index, and what percentage is occupied by the other info, like storing the documents' field values and such. Thanks! Charles On 5/31/06, Monsur Hossain <[EMAIL PROTECTED]> wrote:
When Lucene first issues a query, it caches a hash of sort values (one value per document, plus a bit more if you are sorting on strings), which takes a while. Therefore, when our application first starts up, we issue one query per sort type. As I understand, it doesn't matter what the query is or how complicated it is. Monsur On 5/31/06, Charles Mi <[EMAIL PROTECTED]> wrote: > Is there a way to preload the index into memory when the process starts? > Basically I want to warm up the index before processing user queries. What > are some recommended ways to do this? Thanks. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
