I wouldn't worry about 100-300ms requests being sidelined until and
unless I saw it happening. I realize I also may have been unclear
before: I was measuring response times, not CPU time, if that helps.
--~--~-~--~~~---~--~~
You received this message because you
Hi,
To clarify, this is based on runtime CPU, not datastore CPU. Also, this
shouldn't affect the serving status of your application, it just means that
your app may see some additional latency on a per request basis if it is
serving a large number of CPU intensive requests.
-Marzia
On Tue, Feb
thanks marzia, thats what I needed to hear.
On Feb 26, 12:33 pm, Marzia Niccolai ma...@google.com wrote:
Hi,
To clarify, this is based on runtime CPU, not datastore CPU. Also, this
shouldn't affect the serving status of your application, it just means that
your app may see some additional
Thanks for following through on this, Marzia! That makes a lot more
sense. I really appreciate the diagnosis; you rock!
bFlood, I think the only reason that handler is getting mauled is
because of the 1200ms+ startup costs for initializing a new instance.
Because it's the same handler, the
thanks marzia
I dont want to read too much into Nick's results above but is 30-200ms
now considered to be CPU intensive?
cheers
brian
On Feb 23, 4:20 pm, Marzia Niccolai ma...@google.com wrote:
Hi,
This is done on a per-request basis.
-Marzia
On Mon, Feb 23, 2009 at 12:14 PM, bFlood
Hi,
20ms is not considered CPU intensive, but once you get up in to the
hundreds, it is.
-Marzia
On Tue, Feb 24, 2009 at 5:43 AM, bFlood bflood...@gmail.com wrote:
thanks marzia
I dont want to read too much into Nick's results above but is 30-200ms
now considered to be CPU intensive?
well that seems like a change from previous posts. I thought people
generally quoted 200-300ms as a safe place to be for most of your
requests
On Feb 24, 4:13 pm, Marzia Niccolai ma...@google.com wrote:
Hi,
20ms is not considered CPU intensive, but once you get up in to the
hundreds, it is.
Hi,
Upon some further investigation, it seems that this is the result of the new
handling of CPU intensive requests, more information about which can be
found here:
http://code.google.com/appengine/docs/quotas.html#Request_Limits
Specifically Applications that are heavily cpu-bound, on the other
Hi,
This is done on a per-request basis.
-Marzia
On Mon, Feb 23, 2009 at 12:14 PM, bFlood bflood...@gmail.com wrote:
hi marzia
when this occurs, is the temp governor set for the entire app? or just
the handler that caused the high CPU warning? above, Nick said that
the typical request
