Mathias, For what it's worth, someone using LSP (Lucene Spatial Playground)'s RecursivePrefixTreeFieldType (which uses geohash encoding by default) quoted a 2x performance increase over Solr's built-in LatLonType. To boost the performance further, there are a couple parameters you can tweak. One is distPrec which defaults to 0.025 and reflects an acceptable imprecision of the border of the query shape -- 2.5% of the approximate radius. Maybe you'd be comfortable with 5% or 10% or somewhere in-between. This figure can be specified at query-time. There is another internal number that I've yet to make configurable at the Solr level which is prefixGridScanLevel. If you are interested in exploring LSP further, go check it out and look at the README. It's a bit skimpy right now but I'm happy to elaborate on the performance tuning.
FYI, don't bother using the GeoHashField field type built-in to Solr. The search algorithm for this particular field is a dumb brute-force algorithm. It gives geohashes a bad name. ~ David ----- Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/Improving-performance-for-SOLR-geo-queries-tp3719310p3737861.html Sent from the Solr - User mailing list archive at Nabble.com.
