, thus avoiding the
caching.
Could this be what you're seeing?
Peter
On Feb 18, 2008 4:20 PM, Brian Doyle [EMAIL PROTECTED] wrote:
We've implemented a custom sort class and use it to sort by distance.
We
have implemented the equals and hashcode in the sort comparator. After
running
We've implemented a custom sort class and use it to sort by distance. We
have implemented the equals and hashcode in the sort comparator. After
running for a few hours we're reaching peak memory usage and eventually the
server runs out of memory. We did some profiling and noticed that a
We've written our own custom sorter to be able to sort on the latitude and
longitude fields from the results. We have an index that is about
18million records and 12GB on disk in size. We allocated about 3GB of heap
to the index and with about 1 request to the index every 2 or 3 seconds we
