Hi Waldemar,
The average CPU per request numbers on the dashboard are composed of
CPU used in executing your code (runtime) and API calls (datastore,
urlfetch, image API, etc). When these numbers are high it can indicate
that app resource usage may be inefficient in some areas, so it pays
to track down the cause.
The CPU warnings in the logs include CPU usage from runtime and the
datastore. If you have already taken steps to mitigate causes of high
datastore CPU usage, then the remaining culprit is probably the
runtime code. Profiling can help identify expensive operations in the
app's code.
Thank you,
Jeff
On Oct 24, 3:17 pm, Waldemar Kornewald <[EMAIL PROTECTED]> wrote:
> On 24 Okt., 20:56, Jeff S <[EMAIL PROTECTED]> wrote:
>
> > It sounds like davekor's app might not need to be fixed further if
> > your app is not using very much runtime CPU (in code outside of the
> > datastore). The CPU megacycles for datastore operations do not
> > currently count against the per-request ("High CPU Request") limits.
> > We're working on ways to make this clearer in the Admin Console.
>
> What about the high-CPU warnings on the dashboard (i.e., not the
> logs)? Do they count only the runtime CPU or also the datastore CPU?
>
> Strangely, almost all views that do write operations appear with a
> high-CPU warning on the dashboard ("Avg CPU" column), but don't
> produce any warnings in the logs. What does that mean and can we
> ignore the warning?
>
> Bye,
> Waldemar Kornewald
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
