On Mon, Aug 20, 2012 at 9:43 AM, Barry Hunter <[email protected]> wrote: > > CloudSQL. That is a 'traditional RDBMS' :) > > https://developers.google.com/cloud-sql/
Except as we've experimentally seen when testing Richard's game, Cloud SQL has significant per-instance throughput limits. I don't know why; possibly something to do with the infrastructure between GAE and Cloud SQL? You'll be lucky to get hundreds of updates per second - and that's across the instance, not across any particular piece of data. BTW, yesterday we shut down the 20 backends that Richard needed to collect game scores. They're now getting submitted to three $16/mo node.js instances, each of which alone could handle peak loads and probably more. When the next game client update goes out and they start submitting directly to the node.js instances instead of GAE, he'll be able to shut down most of the ~80 frontend instances currently required. Granted, this is a fairly unusual app, but by surgically using "the right tool for the right job" (tools which do not exist on GAE) we're going from thousands per month to hundreds per month. I don't consider this a condemnation of GAE - I think it's perfectly acceptable to run a hybrid application, and by launching GCE it's clear that Google does too - but it does kinda bother me that there are these GAE components (like backends) that look really useful but have undocumented limitations (like horrible throughput) that effectively render them useless. Worse than useless, because of all the time wasted experimenting with them. 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.
