There are no high CPU restrictions, but you have to worry about it!

When checking feedzshare's "quota detail" last Friday, we found that a statistical item "high CPU requests" has disappeared,
I can't help guessing whether the App Engine team has released another bug or has actually removed the high CPU limit. On Saturday, the App Engine official blog announced no more "high CPU requests "!, The old man quickly posted the Gae and removed the damn high CPU requests.

App Engine team declared that they have adjusted the request processing method,
Now there is no longer a limit that only two CPU-intensive requests are allowed per minute. In addition, the request timeout time is increased to 30 seconds, which is 10 seconds.
These two restrictions are annoying, especially if the request is processedCodeThere is urlfetch, and the time spent by urlfetch is also included in the CPU time spent.

However
The App Engine team only adjusted the restrictions and introduced the concept of active request (I do not remember this restriction in the past,
If you have seen this before, please leave a message to me). The web server of App Engine can only process 30 requests at the same time.
This means that if the average request response time is 1 second, your application can only process 30 requests per second. If you have a request with a response time of 30 seconds,
The other requests will wait. this is fair. Every app has the same resources. You can decide how to allocate them, whether to process more requests or do more for each request.
Static file requests are not restricted. For more information, see the documentation.

To
So far (early on the 16 th), there is still a warning for requests with high CPU consumption in logs, and the message "this request used a high
Amount of CPU... ", but it is not displayed in severity-warning. I do not know if Google will retain the warning information.
I personally hope they can keep it because it is helpful for tunning.

Another improvement this time is that the size of request and response can be 10 MB. it will be of great help to send large images. however, the size of each API call is 1 MB, which means that each item written to memcache is 1 MB.

With this improvement, the document introducing App Engine quotas is also updated. This document introduces the quota of App Engine and how to calculate the quota (how resources are replenished ), after the quota is exceeded, how does Google deal with it (when a resource is depleted)? I suggest you check it out.
Me
We will publish more information about burst limits when we
Release the billing feature in 2009. With the release of the paid version in, Google app
The engine should have removed the preview hat.

Kuber @ feedzshare