Starred it too. Big issue here. - fetch an url + a put() -> 2000 mcycles and more - fetch(100) (+order, filter...) -> 2000 mcycles and more - use import.zip (level = 6 ) -> 2000 mcycles and more - GQL restriction then you need to order by python -> 2000 mcycles and more - etc,...
This quota is really too low : Free Quota HTTP Requests per Day = 650,000 CPU Megacycles per Day = 200,000,000 So the average mcycle/request = (200 000 000 / 650 000) = 300 mcycles. 300 mcycles/req is really low compared to the cost of a basic operation (put, fetch,...). Another things : - I really wonder how it is calculated. As I have always written in another post, it seems that there is no clear relationship between the profiler results and the number of mcycles. You can have a low profiler score and have a warning (CPU quota) and a big profiler score and no warning. So how to optimize ? - It seems that this quota is calculated twice but differently : there is no relationship between the number of mcycles and the Warning (This request used a high amount of CPU....). Example from my log : * 1159mcycles = This request used a high amount of CPU, and was roughly 1.0 times over... * 2030mcycles = no warning ? strange ? no ? If there is no change, my app will be soon offline. Thank you for your answer. Regards On 21 sep, 16:37, Aral Balkan <[EMAIL PROTECTED]> wrote: > Starred it. I agree that this is a big problem. > > The quota system in general is the thorn in Google App Engine's side > and, from a public relations perspective, quite a nightmare. > > Given that most people will check out an application when it's getting > a lot of publicity (and hits), the first experience many people have > with a Google App Engine app is the "Over Quota" message. Not exactly > the first impression you want to make for your shiny new "Cloud" > solution. > > Aral > > On Sep 21, 12:27 pm, mitnickcbc <[EMAIL PROTECTED]> wrote: > > > I have filed a feature request for this issue, if you feel so please > > star it. > > >http://code.google.com/p/googleappengine/issues/detail?id=720 > > > Here is the description: > > > Well, I don't get the purpose for having a High Amount CPU Quota since > > there is already a general CPU Quota. And there are quite a lot of > > problems caused by this quota which restrict my application from > > affording more load. And my application is far away from a 5 million > > month PV app. > > 1. Requests can become a high amount CPU one very easily. A little > > complex request will consume more than 3K mcycles. And what do I mean > > a little > > complex? If you do more than 2 put, or you do a url fetch, or you do a > > query based on an order to select more than 50 model, or you do a put > > on a > > model more than 20 fields, it is that complex. In my case, 80% of the > > requests are that complex and I don't think it can be optimized > > anymore > > since I do need to do put and url fetch. > > 2. Bad visibility to this quota. There is no way we can know when we > > will run out of quota for this. All we got is the warning in admin > > console that > > says our requests are using high amount CPU quota and will soon run > > out of it. > > 3. Doesn't back to normal quickly. I'm using a script to continue > > fetching my data from production and do some offline process. > > Unfortunately I fetch > > too much in one call that I try to get 100 models at a time and which > > makes the request a high CPU one. Soon, I meet quota deny. Then I stop > > my script, > > but after 1.5 hours, I still see quota deny for requests from my > > users. The "Many of the requests to your application are taking a very > > long time. > > Please optimize these requests." warning keeps there even I have > > stopped the script for so long time. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
