The app engine imposes quotas on various parameters to ensure that your app
doesn't hijack the system resources of other's apps and other's apps don't
hijack your app's systems resources.
http://code.google.com/appengine/docs/quotas.html This link will help you
with more info on that.
Thanks,
I understand quota system, but I don't know exact parameters that trigger
additional latency in statement: 'Applications that are heavily CPU-bound
may also incur some additional latency in order to efficiently share
resources with other applications on the same servers.'
Also I don't know
The text for this quota warning originated in 2008 or begin 2009. At
that time there was a more strict quota on CPU usage. Now you use the
warning to locate requests that might be up for an improvement.
Inspect the request with app-stat and rethink the code used.
2010/12/23 Matija
GAE team !? More info.
--
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-appeng...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For
If I remember right, think the coloring scheme is left over from when
there were other quotas in place.
On Fri, Dec 17, 2010 at 03:09, Matija matija.jerko...@gmail.com wrote:
Are you sure about this ? I have noticed that I did indeed get
new additional instance, but are their automatic
Yes, I remember this. But after removal of 'high cpu quota' there was no
(spoken) penalty for over 1000 ms request latency (beside bad user
UI experience) and now it is inability to get new instances.
If you look at Quotas and
