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. -- Alex
On Jul 15, 4:14 am, Anthony Mills <[email protected]> wrote: > On Jul 14, 6:48 am, Anthony Mills <[email protected]> wrote: > > > I'll do some testing later tonight about what happens when > > REQUEST_SIZE is 1, 5, 10, 20, etc., and report back. > > Ok, here are a selection of the results of my tests. "rs" controls the > number of results asked for. > > /service?a=g&t=m&rs=1 200 32ms 39cpu_ms 31api_cpu_ms > /service?a=g&t=m&rs=2 200 44ms 50cpu_ms 44api_cpu_ms > /service?a=g&t=m&rs=3 200 56ms 64cpu_ms 57api_cpu_ms > /service?a=g&t=m&rs=4 200 101ms 82cpu_ms 70api_cpu_ms > /service?a=g&t=m&rs=5 200 53ms 90cpu_ms 84api_cpu_ms > /service?a=g&t=m&rs=6 200 50ms 109cpu_ms 97api_cpu_ms > /service?a=g&t=m&rs=7 200 41ms 117cpu_ms 110api_cpu_ms > /service?a=g&t=m&rs=8 200 57ms 136cpu_ms 123api_cpu_ms > /service?a=g&t=m&rs=9 200 43ms 144cpu_ms 136api_cpu_ms > /service?a=g&t=m&rs=10 200 62ms 174cpu_ms 150api_cpu_ms > /service?a=g&t=m&rs=20 200 47ms 306cpu_ms 282api_cpu_ms > /service?a=g&t=m&rs=50 200 76ms 705cpu_ms 678api_cpu_ms > /service?a=g&t=m&rs=70 200 86ms 974cpu_ms 942api_cpu_ms > > Interesting. The variable api_cpu_ms climbs very ... predictably. In > fact, it would seem: > > api_cpu_ms = 13.2 * results + 17.5 > > ... rounded off to the nearest millisecond. At least for queries. I > haven't tried straight key fetches. > > This is really disturbing. > > // Anthony --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
