>> >> If worried about performance, defer the updates using the task queue. >> (so the actual increment is done by a task after the actual request >> has finished to the user) > > because the current system it's replacing, has at least 60 files access per > sec > during working hours. so that translates to 60 data counter increment > in the datastore.
60 'events' is nothing. AppEngine can scale to thousends of QPS. The limit is when the same counter - ie the same Entity, needs updating many times a second. The limit applies also to entity groups. But you need a counter per file, per customer. So as long as the same user is not downloading the same file 5 times a second, then not really an issue. Even if you put each customer in an entity group - do you have single users downloading 5+ files per second? -- 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.
