HR does have a slightly higher latency which would reduce the rate a little, but 1/second is to leave a safety margin. In practice you'll probably be able to get more, but you should not design an app assuming you'll be able to sustain 5 writes to an entity group per second.
Robert On Wed, Mar 2, 2011 at 11:43, Spines <[email protected]> wrote: > The using the HR datastore page (http://code.google.com/appengine/docs/ > python/datastore/hr/overview.html) says: > > "This allows queries on a single guestbook to be strongly consistent, > but also limits changes to the guestbook to 1 write per second (the > supported limit for entity groups)". > > I remember reading a while ago (before the HR datastore existed) that > you could get about 1 to 5 writes per second to an entity group. > > Is the supported writes per second to an entity group less on the HR > datastore? > > -- > 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. > > -- 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.
