Well as to point #1 below, wouldn't you know as I wrote that post I got my first warning in the logs. I see it is different from the exclamation icon.
01-20 12:29PM 15.424 /regions/ 200 1601ms 3270ms-cpu 7kb 69.63.176.230 - - [20/Jan/2009:12:29:17 -0800] "POST /regions/ HTTP/ 1.1" 200 7612 - - W 01-20 12:29PM 17.022 [W] "This request used a high amount of CPU, and was roughly 3.7 times over the average request CPU limit. High CPU requests have a small quota, and if you exceed this quota, your app will be temporarily disabled." Now this was for a request that did a single query to load 3 small entities, and didn't even write anything at all to DS. I'm actually seeing other timing warnings, so I hope it's GAE stuttering in general. I'm beginning to worry that this platform isn't going to work out for anything other than serving the most basic pages right out of memcache. On Jan 20, 12:39 pm, boson <[email protected]> wrote: > Hi Marzia, thanks for responding. I've read that a few times actually > and it's part of what is confusing. See: > > 1. > Re:http://code.google.com/appengine/kb/general.html#highcpu > That link describes a message that says: > "This request used a high amount of CPU, and was roughly > X times over the average request CPU limit. > High CPU requests have a small quota, and if you exceed > this quota, your app will be temporarily disabled." > > However I get the orange/red text in my req log with yellow ! icon > saying (on mouseover): > "This request used a high amount of CPU and may soon exceed its > quota" > > I've never seen the one from the docs. Is this the same message & the > docs are out of date, or is this a different message with a different > meaning? > > 2. > Also, the other issue: if a single Datastore put (an update) of a > modestly sized (<10 fields) entity is often taking ~1000ms-CPU > (=1sec), I understand that doesn't count toward runtime CPU quota > (right?), but it DOES count toward overall CPU Time used. > > So 3600 puts would take a ~CPU-hour, which costs $0.10 at the proposed > rates. That's ~$0.027 / 1000 hits, assuming a page writes just one > entity (eg counter/timestamp/etc). > > It seems like (social/consumer-oriented) apps on GAE would need dozens > of ads just to break even to support the basic DS operational costs, > not even including any other costs (bandwidth, additional CPU use for > preparing/rendering pages, etc.). > > Tell me my math is wrong, or that DS puts are going to be optimized > soon? > I'm just having a hard time seeing how writing a single entity takes > so much CPU. > > Thank you. > > On Jan 20, 9:35 am, Marzia Niccolai <[email protected]> wrote: > > > Hi, > > > Please also read this > > FAQ:http://code.google.com/appengine/kb/general.html#highcpu > > > -Marzia --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
