On Wed, Jun 13, 2012 at 11:33 AM, Brandon Wirtz <[email protected]> wrote: > I know exactly how much every request cost me. > > cpm_usd=0.000308 > > cpm_usd=0.000175
These numbers tell you how much a request cost, but don't tell you how much another identical request will cost. Also, what do these numbers mean in the context of a multithreaded instance? If you have 5 requests running in one instance and the 6th request hits a fresh instance, how are the costs divided among the 6 requests? > As to the latency changes in pricing are no different than when AWS has a > performance issue. (actually less so) In AWS, a performance degradation in the cluster may reduce your application effectiveness, but it doesn't change billing - at least not automatically. Maybe it will cause you to spin up new instances, but this doesn't seem particularly likely - at least not in a multithreaded world. A java appserver can easily handle hundreds (even thousands) of requests blocked on IO, so even under increased "datastore" (lets say DynamoDB or SimpleDB) latency there's no reason to expect a need for lots of extra instances. Theoretically, GAE's multithreaded instances should work the same way... except that they don't for some reason. 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.
