Chris's response is quite good, and I have a couple things to add: 1. Since you can tolerate 1km slop, try defining the dynamic field *_coordinate as tfloat instead of tdouble. This will halve your memory requirements, but I'm not sure if it will be any faster -- it's worth a shot since you've already indicated that your requirements don't call for a double. Information I've read vary on exactly what is the accuracy of float vs double but at a kilometer there's no question a double is overkill.
2. Try my Solr 3.x spatial plugin called "SOLR-2155" at github: https://github.com/dsmiley/SOLR-2155 It is very fast at filtering (even for circles) as indicated in this stackoverflow thread: http://stackoverflow.com/questions/11636376/solr-performance-on-ec2-for-geospatial-queries in which it destroys LatLonType in a big data speed test :-D. You should be happy to know that this technology is on its way into Solr 4, albeit not quite yet. Cheers, ~ David Smiley ----- Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/Tuning-caching-of-geofilt-queries-tp3998975p4000525.html Sent from the Solr - User mailing list archive at Nabble.com.
