On Jul 16, 12:45 pm, Alexander Trakhimenok <[email protected]> wrote: > This is expected behavior and nature of GAE data store. > > This is the beauty that the time will consistent and have direct > relations to number of items retrieved and not depend on number of > records stored.
I understand that it is important to have a consistent response time, and maybe a charge of of api_cpu_ms = x * results + y could make sense, but as it currently is, it's crazy. It's claiming 13.2 ms /per result/. It's saying that the overhead of a request is roughly the same as fetching one extra result. I would have expected x to be lower and y to be higher. Even more than that, it's saying it costs Google's datastore 1000 ms to retrieve a 75-result indexed query. So I guess this means batching really doesn't matter. No point in trying to do one longer request when two shorter ones can be done. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
