you can shard by the biggest geocell and cache based on the smallest geocell.
at then end GeoModel creates a hash based on geoboxes that you can easily play with On 14 May 2011 18:10, Devraj Mukherjee <[email protected]> wrote: > Hi all, > > Our project http://safesharps.org.au uses GeoModel > (http://code.google.com/p/geomodel/). To boost performance we have > been caching many of our query results using memcache, this is > generally done by keeping an index of the search terms. > > Our app has Web / Mobile Web and upcoming mobile applications for iOS > and Android. > > Geo is a little tricky to cache, since using the Lat/Lng is not > exactly efficient. For example, a search query by people within 10 > meters of each other would result in the same results on our database > but would have different Geo locations. > > Any ideas on caching / performance enhancement when using Geo queries? > > Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- http://about.me/david.mora -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
