HR supports writes to the same Entity at 1 time per second. You can write around these limitations.
You are approaching the problem wrong. Entities shouldn't be updated multiple times per second because you don't know the order of arrival, internet latency can cause jitter, and your data would be invalid. You should be using transactions and incrementing then auditing. And you should be using Ram and Memcache to speed up reads and help with buffering writes. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Romanov Sent: Saturday, December 10, 2011 9:40 PM To: Google App Engine Subject: [google-appengine] Datastore question 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. -- 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.
