On Tue, Nov 25, 2008 at 7:49 AM, souravm <[EMAIL PROTECTED]> wrote: > > 3. Another case is - if there are 2 search requests concurrently hitting > the server, each with sorting on the same 20 character date field, then also > it would need 2x2GB memory. So if I know that I need to support at least 4 > concurrent search requests, I need to start the JVM at least with 8 GB heap > size. >
This is a misunderstanding. Yonik said "searchers", not "searches". A single searcher handles all live search requests. When a commit/optimize happens, a new searcher is created, it's caches are auto-warmed and then swapped with the live searcher. It may be a bit more complicated under the hoods, but that's pretty much how it works. Considering that after commits and during auto-warming, another searcher might have been created which will have another field cache for each field you are sorting on, you'll need double the memory. The number of searchers can be controlled through the "maxWarmingSearchers" parameter in solrconfig.xml -- Regards, Shalin Shekhar Mangar.
