You should expect 1/s write rate, though it's possible to have a higher rate.
-- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Thu, Jan 6, 2011 at 1:18 AM, Matija <[email protected]> wrote: > I have found this old (but universal) > article<http://code.google.com/appengine/articles/sharding_counters.html> that > deals with contention problem where first paragraph is: > > "...When developing an efficient application on Google App Engine, you need > to pay attention to how often an entity is updated. While App Engine's > datastore scales to support a huge number of entities, it is important to > note that you can only expect to update any single entity or entity group > about *five times a second*. That is an estimate and the actual update > rate for an entity is dependent on several attributes of the entity, > including how many properties it has, how large it is, and how many indexes > need updating. While a single entity or entity group has a limit on how > quickly it can be updated, App Engine excels at handling many parallel > requests distributed across distinct entities, and we can take advantage of > this by using sharding. ..." > > Matija > > -- > 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]<google-appengine%[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.
