Why can’t I configure how many requests Frontends handle? F1’s serving 8
requests is silly. F4’s handling 8 requests is often equally silly in the
opposite direction.
Good idea. I have created a feature request for it, Please star it:
On Sunday, July 29, 2012 12:43:31 PM UTC-7, Brandon Wirtz wrote:
Why can’t I configure how many requests a backend can handle? Or have a
back end act like a front end and handle 8?
The Java version has an experimental field in backends.xml called
max-concurrent-requests. I would assume
Same question for task queue health status, or any kind of programmatic
access to the last measured value (+ maybe 5 min average) by the system
status for any service / type from: http://code.google.com/status/appengine
In my use case I would be highly interested in reading the current add to
On Mon, Jul 30, 2012 at 11:15 AM, Marcel Manz wrote:
Certainly I could measure those latencies myself and store the information
in memcache for subsequent requests,
I would think you would have to. AppEngine is massively distributed,
operating out of multiple data-centres.
So the latencies
It would be good to get an explanation from Google on how the system status
is probed (please excuse me if this is explained somewhere, I haven't yet
come across detailed info on this topic). Eg. is this one and the same
instance in just one data center probing such times or are these
