@davew: As Sylvain points out, below, the simplest things can cause this. I've had straight-to-template calls cause high CPU errors and, to tell you the truth, even if I could meaningfully profile Django templates, I don't think there's much I could do about it. Especially, as Sylvain states, it appears to be random.
Aral On Oct 4, 9:30 am, Sylvain <[EMAIL PROTECTED]> wrote: > @davew : "If you don't know what causes the problems, then find out? > Is it in > your code? Is it a datastore put timeout? Profile it? " > I've spent a lot of time to understand it too. And I realize that you > can raise this Quota Warning in 2 lines : > myModel.all(), myModel.fetch(100). So here, there is nothing to > optimize or to profile, particularly when it is random. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
