It could be your index has an unusual number of unique terms.
If you can upgrade to the latest 3.x, the RAM used by the terms index
has been very substantially reduced...
If not, try setting the termInfosIndexDivisor to eg 2 or 3 ... this
will load 1/2 or 1/3 of the indexed terms into RAM, but ma
Have you tried a System.gc before opening the index? And check how much
memory is available before the open. Does the open seem to be taking more
memory that could reasonably be expected? How big is the index, how many
docs, how many unique terms in that index?
1.8G doesn't sound like a lot. Y
