Thanks, Brandon, this is great info! This plus Stephen's info shows how to get scalability without concurrency:
No, the way it currently works is if your apps latency > 1000ms (figures of 800-900ms have also been mentioned) it won't scale. The lower the latency the more they scale it. So the incentive has always been to write low latency apps. On Friday, May 20, 2011 1:44:22 AM UTC+8, Brandon Wirtz wrote: > > >The 50k free database operations is a bit more nebulous since Google are > still scratching their heads over it. With correct memcache usage it really > should be enough, although that might be a bit of wishful thinking and > obviously depends significantly on your use case. > > > > > > As reference… > > > > Datastore API Calls > > [image: Description: 0%] > > 0% > > 183,470 of Unlimited > > Okay > > Memcache API Calls > > [image: Description: 0%] > > 0% > > 323,702 of Unlimited > > Okay > > > > Twice as many memcache calls as data store. This is pretty consistent > across my apps. > > > > My average Entity is about 5k… (this says a little lower) > > > > ** > > *Entity Kind* > > *# Entities* > > *Avg. Size/Entity* > > *Total Size* > > Kind1 > > 627,354 > > 4 Kbytes > > 2 GBytes > > > > > > Every request I have uses potentially: > > > > Configuration load: 1 memcache read OR 1 datastore read and 1 memcache > write > > > > Get Content: 1 memcache Read, OR 1 datastore Read, 1 Memcache Write, OR 1 > DataStore Write, 1 Memcache write > > > > > > I don’t know if this helps anyone, but I’m always interested in how apps > use their quotas, so I thought I would share. > > > -- 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.
