On Mar 6, 7:14 pm, Brandon Thomson <[email protected]> wrote:
> They said it has been "stabilized." But I agree, it is still much
> worse. The timeouts are the real problem; it's just impossible to
> complete certain operations.
I get timeouts trying to put single entities into the datastore
(sometimes). These aren't big objects -- maybe a total size of 3k
bytes with 3 indexes. I also get timeouts just paging through result
sets -- i.e. when doing 'for (doc in doclist):' where doclist is
the result of filter operation.
It clearly is doing something when these timeouts happen as the CPU
time used is *much* higher than normal. Alternatively, maybe there is
a bug, and something goes into a hard loop that is only broken when
the timeout expires....... It would be nice to know whether the CPU
that we are being charged in these timeout cases is *real* CPU that
was actually consumed somewhere, or whether this is a notional CPU
charge for what "must have been happening -- but actually wasn't". If
the former, then I'd like to understand what was actually going on to
consume all of these CPU cycles.
Philip
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
