On Nov 21, 2007 11:06 AM, Chris Laux <[EMAIL PROTECTED]> wrote: > Now when I reduce the size of caches (to a fraction of the default > settings) and number of warming Searchers (to 2),
Set the max warming searchers to 1 to ensure that you never have more than one warming at the same time. > memory use is not > reduced and the problem stays. Only deactivating auto-warming will help. > When I set the heap size limit higher (and go into swap space), all the > extra memory seems to be used up right away, independently from > auto-warming. > > This all seems to be closely connected to sorting by a numerical field, > as switching this off does make memory use a lot more friendly. How many documents are in your index? If you don't need range queries on these numeric fields, you might try switching from "sfloat" to "float" and from "sint" to "int". The fieldCache representation will be smaller. > Is it normal to need that much Memory for such a small index? Some things are more related to the number of unique terms or the numer of documents more than the "size" of the index. -Yonik
