Sorting creates a large array with "roughly" an entry for every document in the index. If it is not on an 'integer' field it takes even more memory. If you do a sorted request and then don't sort for a while, that will drop the sort structures and trigger a giant GC.
We went through some serious craziness with sorting. On Fri, Jan 30, 2009 at 3:54 PM, wojtekpia <wojte...@hotmail.com> wrote: > > I profiled our application, and GC is definitely the problem. The IBM JVM > didn't change much. I'm currently looking into ways of reducing my memory > footprint. > > -- > View this message in context: > http://www.nabble.com/Performance-%22dead-zone%22-due-to-garbage-collection-tp21588427p21758001.html > Sent from the Solr - User mailing list archive at Nabble.com. > > -- Lance Norskog goks...@gmail.com 650-922-8831 (US)
