Re: [google-appengine] Caching GeoModel requests?
You should compute the GeoBox for your location, and then query/cache the geobox. Take a look inside the geomodel source code for geoboxes. You might have to modify the geomodel source code. Thanks, Rodrigo Souza On Sat, May 14, 2011 at 8:26 PM, David Mora wrote: > 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 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 google-appengine@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com. >> 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 google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Caching GeoModel requests?
Appreciate that Brandon. On Sun, May 15, 2011 at 10:24 AM, Brandon Wirtz wrote: > Round. > > http://maps.google.com/?ie=UTF8&ll=47.595,-122.36&spn=.873914,.712402&t=h&z= > 15 > > 3 decimals of accuracy puts the boat near the center, but would you change > results if you > Were closer to the peer? > > http://maps.google.com/?ie=UTF8&ll=47.589,-122.37&spn=.873914,.712402&t=h&z= > 15 > > Essentially, 47.6 , -122.35 is the same as any of the above values. > > Pick the level of accuracy you need and round to that. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Caching GeoModel requests?
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 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 google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
RE: [google-appengine] Caching GeoModel requests?
Round. http://maps.google.com/?ie=UTF8&ll=47.595,-122.36&spn=.873914,.712402&t=h&z= 15 3 decimals of accuracy puts the boat near the center, but would you change results if you Were closer to the peer? http://maps.google.com/?ie=UTF8&ll=47.589,-122.37&spn=.873914,.712402&t=h&z= 15 Essentially, 47.6 , -122.35 is the same as any of the above values. Pick the level of accuracy you need and round to that. -Original Message- From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Devraj Mukherjee Sent: Saturday, May 14, 2011 5:10 PM To: google-appengine@googlegroups.com Subject: [google-appengine] Caching GeoModel requests? 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
