I still don't understand one aspect of Google's approach - regarding CPU limits. For example, consider my application, a personal organizer. Each page view needs to tie together disparate entities; there are lots of writes; etc. The final result of the application is the creation of reports (using reportlab). Here, I need to make some queries, perform some calculations, etc.
In setting up the organizer, there are several tasks that are somewhat large. I get CPU warnings for being, say, 3-5 times over the average limit. Some common pageviews are right around the limit (1.0, 1.1 times over the limit). Finally, when generating reports, I might get some warnings that my app is 4-5 times over the limit. The question is: is an application of my sort suitable for Appengine? Obviously, I'll optimize, and hope to get a majority of my common pageviews into limits. But it is inevitable that a significant percentage of requests will exceed CPU quotas. I am willing to pay money for exceeding quotas... There is still a significant amount of development ahead. If it appears that my task is a non-starter for Appengine, I'd prefer to switch to pure django earlier rather than later. Can anyone provide some enlightenment for my dilemma? Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
