Brian, If you are getting the big time on the first run after a few minutes, could it be the "cold start issue"? If the second run is immediately after the first it may be fetching cached results.
Our queries are typically stable across requests. I have not tried running the same query repeatedly in one request though. Robert On Wed, Feb 24, 2010 at 9:34 AM, bFlood <[email protected]> wrote: > hi all > > I'm seeing some pretty random spikes in Query times on simple gql > statements. Run it once, it take 5000+ms (real) and then immediately > run it again and it takes 169ms. Anyone else seeing huge spikes in in > simple datastore_v3.RunQuery requests? > > some other data: > 1) there are only a few other concurrent requests so this is not the > 30 concurrent operation limit > 2) these are not deadlines or cold starts either, this is definitely > occuring on the RunQuery call > 3) app stats is setup for debugging if needed > > cheers > brian > > -- > 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. > > -- 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.
