2 ms·
It means that GAE is horribly, amazingly, inefficient. This. We always knew GAE was inefficient. There's no doubt about that. Serving 30 or 40 requests per sec
by bane 15y ago
It means that GAE is horribly, amazingly, inefficient.
This. We always knew GAE was inefficient. There's no doubt about that. Serving 30 or 40 requests per second would spawn quite a few instances and start producing request errors.
This is a load a 4 year old machine could handle with ease.
Why did we put up with this? Because Google didn't make us pay for the crappiness -- the pricing made sense. You don't pay Ferrari prices for a slow car...and during a surge it scales up gracefully. Go from 30 rps to 1000 rps and it'll just work. An old machine co-located someplace won't do that.
Now under the new pricing gouge Google is making us pay for their inefficiencies. All appearances are that this is what this really costs (plus some reasonable markup)...well that's pretty piss poor. Because we're essentially paying to haul cargo in a Ferrari and it's dumb dumb dumb.
- DanielChatfield 15y agoIt would only start producing request errors if there was bad coding. Many of Google's stuff (like the chrome updates) are done through GAE and receive no "special treatment" from GAE (except lifting the request limits which wouldn't affect any sites you make). GAE was made to be fast - and it is. It was made to be reliable - and it is (100% uptime in over 500 days).
- buff-a 15y agoPostmortem for August 18, 2011 outage http://groups.google.com/group/google-appengine-downtime-notify/browse_thread/thread/4f0be3699386a305 http://groups.google.com/group/google-appengine-downtime-not...