I am not sure where you are getting your data; get by id averages less than 50ms consistently, with only very rare spikes towards 100ms. In the last week, for example, latency has not gone over 100ms at all.
Regarding the query, I still don't know what you mean. Inequality filters on multiple properties are still not allowed, as far as I can tell. The "distance" function you use in the query would be absolutely kick-ass if it existed, but as far as I know, something like that is only currently avalilable in the search API. On Wednesday, August 8, 2012 1:39:01 PM UTC-4, Brandon Wirtz wrote: > https://developers.google.com/appengine/docs/python/datastore/queries > > Shows examples of <> which can be stacked, and “In List”. You can also do > calculated/weighted values where you say +4 if red and -2 if blue. > > Get by ID should be around 150MS if you use the ID. 100ms is minimum > typically it trends up to 350ms. GAE has to be having a bad day for GetbyID > /key to be more than 500ms. > > We are seeing 8MS average on fetches from backends In instance memory. And > for Static large data sets we have code that list literally as simple as > > this = ‘that’ > That = ‘this’ > Shipping400lbsto90201 = ‘345.97’ > > Which is very close to a no-op. > > Our spin up time for a 100 meg static data set is 4s. Best of 100,000 > requests was 3ms worst of was 114ms (again with an average of 8ms) -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/pmdzcw8FZesJ. 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.
