If you can tolerate some minimal level of error, like when you are counting popularity, this works great: http://blog.notdot.net/2010/04/High-concurrency-counters-without-sharding
-Sebastian http://studio.livemade.com On Sep 7, 1:28 am, Robert Kluin <[email protected]> wrote: > Shard when you are updating the same entity multiple times per second. > Various numbers have been stated, but it is usually something around > 3 writes to the same entity per second. > > Robert > > > > > > > > On Mon, Sep 6, 2010 at 23:48, Mark <[email protected]> wrote: > > Hi, > > > I cannot find this statistic, I think I read it somewhere in the app > > engine docs - what's the write throughput app engine advertises, and > > is there any recommendation as to what point we should think about > > things like sharded counters? > > > For example, I need to keep a counter of some action, I have a class > > dedicated for that purpose. I don't expect more than one write per > > hour on it, so there's no need to think about sharding it. But is > > there any rule out there to let us know when we should start moving to > > a sharded counter? > > > Thanks > > > -- > > 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 > > athttp://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.
