On Wed, Dec 14, 2011 at 4:43 AM, Brian Quinlan <[email protected]> wrote: > > It is possible that a small increase in datastore latency slowed down > your application enough that more instances were needed to service > requests.
I hate to dig up an old subject, but this is exactly the biggest concern I have with GAE's pricing model. When Google screws up the datastore, revenue goes up. I don't think anyone at Google is so nefarious that they would deliberately increase datastore latency, but in the long run behavior follows incentives. And this seems like a strong incentive *not* to fix latency issues. In the made-for-tv movie script, some executive deliberately lets latency rise in the last few days of the quarter just to make his revenue targets and get a bonus. And because of this, some otherwise-friendly, normal schizophrenic's medication order fails to process and he goes on a murderous rampage in NYC. And Sam Waterston convenes a grand jury....ok ok, so I've been watching too much Law And Order. It would make me a lot happier if "time spent waiting for Google services which we are already paying for" (ie, datastore operations) was subtracted from instance hours we pay for. What this says is datastore latency is Google's problem, not my problem. It means that GAE engineers will be always be working extra hard to keep latency down - because low latency improves Google's bottom line rather than inflating it. Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
