3 ms·
For what it's worth, Google App Engine uses a so-called "intelligent" global request queue/scheduler. In most circumstances it's quite effective.
by dylanvee 14y ago
For what it's worth, Google App Engine uses a so-called "intelligent" global request queue/scheduler. In most circumstances it's quite effective.
- vetrom 14y agoSource please?
- dylanvee 14y ago"Pending request latency arises when all of your application's available instances are too busy to serve new requests. When this happens, incoming requests go to a pending request queue." https://developers.google.com/appengine/docs/adminconsole/performancesettings#scheduler https://developers.google.com/appengine/docs/adminconsole/pe... Pending latency is exposed as a metric on the App Engine Dashboard.
- latchkey 14y agoIt is effective, but not without problems. http://code.google.com/p/googleappengine/issues/detail?id=7865 http://code.google.com/p/googleappengine/issues/detail?id=78... http://code.google.com/p/googleappengine/issues/detail?id=5755 http://code.google.com/p/googleappengine/issues/detail?id=57... http://code.google.com/p/googleappengine/issues/detail?id=7836 http://code.google.com/p/googleappengine/issues/detail?id=78... Needless to say, it is VASTLY better than Heroku's router. You'll never see an H12 error with GAE.
- dylanvee 14y agoIndeed, while having a global request queue is good, the scheduler's one-size-fits-all behavior can sometimes be suboptimal. Thankfully there are several ways in which it can be tuned: https://developers.google.com/appengine/docs/adminconsole/performancesettings#scheduler https://developers.google.com/appengine/docs/adminconsole/pe...