You may also have a slight misconception - the write limit applies to each individual entity, not the entity as a class. So you can only update Thing1 once per second, but you can also update Thing2 once per second, etc. You should have no problem being able to "handle creation of lots of same entities" as long as you don't explicitly put them in a single entity group. Jeff On Sun, Dec 11, 2011 at 1:39 AM, Andrew Romanov <[email protected]> wrote: > I am thinking of using Google App Engine for next web application, but > have some concerns about Datastore (High Replication Datastore). In > video explaining High Replication Datastore they told that writes take > some time (45 ms). As I understand that means that many users won't be > able to update some entity more than 22 times a second. It doesn't > sound too scary. But what if that's task management system with lots > of users. Will I be able to handle creation of lots of same entities > (tasks) or will I run into same 22 writes a second limit? If so, what > solution would you suggest? > > -- > 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. >
-- We are the 20% -- 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.
