Takashi, is there some more detailed information on why Google doesn't encourage using a connection pool? Is it simply to encourage allowing the db instance to wind down instead of being kept alive only by pool connection health checks? If so I'm sure it could be configured to avoid this.
It does seem to me that it could reduce Richard's costs drastically, by 2/3 just on the writes to the db by his own numbers. I've been using pooling without issue for several months now, though admittedly with very little traffic so far, so if you think this is going to get me in trouble later I'm very eager to hear why. On Fri, Aug 3, 2012 at 12:28 AM, Richard Watson <[email protected]>wrote: > What are the performance characteristics of connecting to Google Compute > Engine? Maybe slap the in-memory app onto that. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/pTFagZqQkx4J. > > 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. > -- 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.
