It's a physical limitation duo to the disk seek time. An entity can be updated at most about 5 times/sec (the data is from a session of Google I/O which name I can't remember now), so does an entity group. Considering other problems, you should assume it's not safe to update an entity group more than 1 time/sec.
---------- keakon My blog(Chinese): www.keakon.net Blog source code: https://bitbucket.org/keakon/doodle/ On Thu, Jan 6, 2011 at 4:15 PM, Matija <[email protected]> wrote: > At the end of > article<http://code.google.com/appengine/docs/python/datastore/hr/overview.html> > there > is statement that ''... but also limits changes to the guestbook to 1 write > per second (the supported limit for entity groups). ...'. > > I understand contention problems, etc. Is this limit somehow imposed or > simply it is statistical information for entity group put latency (two > entities in same entity group) ? > > -- > 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.
