> Imagine the potential consequences if any app could consume as much > resources as it sees fit at any time from that daily quota it has. > Peak load could (and would) go up unpredictably, and that would > potentially cause problems even to apps that are more optimized than > the CPU hogs. Remeber that this is a shared system, so these barriers > are necessary.
A main point of App Engine is to let any app potentially consume as much resources as it needs at any time whether it's from a slashdotting or a lower volume of high CPU requests. I look at the High Amount CPU quota warnings as an information service to help tune your app. After pay-as-you-go is released, these warnings should be purely informational IMHO. High CPU requests will cause slow responses, which is a reason to tune those requests, but you shouldn't get an error. I'm hitting the High Amount CPU warnings on a site that's not even close to daily quotas. It's been helpful to see the flags for specific URLs so I can tune them. For example, I've got an AJAX client that loads in JSON data for a specific "workshop" model. My current model can produce, in one request, the JSON for all submissions in all meetings for that workshop, so it goes three models deep in queries. Now that I see the bottleneck, I'm making the data transfer less chunky. So my AJAX client will issue separate GETs for the models, which is one way around High CPU requests -- make the transactions more granular and use AJAX on the client-side to piece together the supplied data. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
