I suspect that it is "real CPU" that is unfortunately not doing any useful work. For example when you commit a transaction on a highly contentious entity, you may need to retry 50 or more times before succeeding. Each try wastes the same amount of CPU, but you only succeed in committing the transaction once.
It's weird, I know. As to why so much CPU is being wasted now is anybody's guess; Google won't tell us what they changed. On Mar 8, 1:07 pm, WeatherPhilip <[email protected]> wrote: > 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
