Re: Term Dictionary taking up lots of memory, looking for solutions, lucene 5.3.1

2017-07-02 Thread David Smiley
If there are no filters, then LatLonDocValuesField is going to be asked to sort all of your docs, which is obviously going to take awhile. Can you simply add a filter? Like a distance filter using LatLonPoint? On Thu, Jun 29, 2017 at 11:49 AM sc wrote: > Hi, > >I have similar requirement o

Re: Term Dictionary taking up lots of memory, looking for solutions, lucene 5.3.1

2017-06-29 Thread sc
Hi, I have similar requirement of searching points within a radius of 50m. Loaded 100M latlon, indexed/searching with LatLonDocValuesField. I am testing it on my macbook pro. I have used all Directory(RAM/FS/MMap) types but it takes 3-4 secs to do search/sort to return of 5 points with in rad

Re: Term Dictionary taking up lots of memory, looking for solutions, lucene 5.3.1

2017-06-14 Thread David Smiley
Nice! On Tue, Jun 13, 2017 at 11:12 PM Tom Hirschfeld wrote: > Hey All, > > I was able to solve my problem a few weeks ago and wanted to update you > all. The root issue was with the caching mechanism in > "makedistancevaluesource" method in the lucene spatial module, it appears > that documents

Re: Term Dictionary taking up lots of memory, looking for solutions, lucene 5.3.1

2017-06-13 Thread Tom Hirschfeld
Hey All, I was able to solve my problem a few weeks ago and wanted to update you all. The root issue was with the caching mechanism in "makedistancevaluesource" method in the lucene spatial module, it appears that documents were being pulled into the cache and not expired. To address this issue, w

Re: Term Dictionary taking up lots of memory, looking for solutions, lucene 5.3.1

2017-05-18 Thread Uwe Schindler
Hi, Are you sure that the term index is the problem? Even with huge indexes you never need 65 good of heap! That's impossible. Are you sure that your problem is not something else?: - too large heap? Heaps greater than 31 gigs are bad by default. Lucene needs only few heap, although you have lar

Re: Term Dictionary taking up lots of memory, looking for solutions, lucene 5.3.1

2017-05-18 Thread Michael McCandless
That sounds like a fun amount of terms! Note that Lucene does not load all terms into memory; only the "prefix trie", stored as an FST ( http://blog.mikemccandless.com/2010/12/using-finite-state-transducers-in.html), mapping term prefixes to on-disk blocks of terms. FSTs are very compact data str

Re: Term Dictionary taking up lots of memory, looking for solutions, lucene 5.3.1

2017-05-17 Thread Adrien Grand
Is upgrading to Lucene 6 and using points rather than terms an option? Points typically have lower memory usage (see GeoPoint which is based on terms vs LatLonPoint which is based on points at http://people.apache.org/~mikemccand/geobench.html#reader-heap). Le jeu. 18 mai 2017 à 02:35, Tom Hirschf