ironically, it was one of my initial "push back" on this that makes that not doable.
I had offered that we'd offer stats instead of per file, just per customerId as a beginning point. so basically we'd have 1 entity per customerId. and just +1 the counter on a per customerId. So while a customer won't download the same file 5 times per second, the customer will very likely download 5 different files per sec, thereby causing the issue of updating the same entity multiple times per sec. On Mon, Apr 9, 2012 at 5:25 PM, Barry Hunter <[email protected]> wrote: > 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? -- Omnem crede diem tibi diluxisse supremum. -- 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.
