Re: Memory consumed by IndexSearcher

2009-09-23 Thread Karl Wettin
23 sep 2009 kl. 17.55 skrev Mindaugas Žakšauskas: I was kind of hinting on the resource planning. Every decent enterprise application, apart from other things, has to provide its memory requirements, and my point was - if it uses memory, how much of it needs to be allocated? What are the bounda

Re: Memory consumed by IndexSearcher

2009-09-23 Thread Karl Wettin
23 sep 2009 kl. 17.55 skrev Mindaugas Žakšauskas: Luke says: Has deletions? / Optimized? Yes (1614) / No Very quick response, try optimizing your index and see what happends. I'll get back to you unless someone beats me to it. karl

Re: Memory consumed by IndexSearcher

2009-09-23 Thread Mindaugas Žakšauskas
Hi Karl, On Tue, Sep 22, 2009 at 6:58 PM, Karl Wettin wrote: > <..> Thing that > consume the most memory is probably field norms (8 bits per field and > document unless omitted) and flyweighted terms (String#interal), things you > can't really do that much about. I was kind of hinting on the res

Re: Memory consumed by IndexSearcher

2009-09-22 Thread Karl Wettin
Hi Mindaugas, it is - as you sort of point out - the readers associated with your searcher that consumes the memory, and not so much the searcher it self. Thing that consume the most memory is probably field norms (8 bits per field and document unless omitted) and flyweighted terms (Strin

Memory consumed by IndexSearcher

2009-09-21 Thread Mindaugas Žakšauskas
Hi, I was wondering what would be sensible amount of memory IndexSearcher can consume? In my application we do retain reference to it for quicker searches; however I have become a bit worried for it being a memory hog. We are using Lucene 2.4.0 on 8 CPU Linux SMP box; JVM is Sun's 1.6.0_14 64-Bit