I think Nick told this group that if you have to update the object 1 or 2 times per second there is no need to use sharded counters. It just depends on how rapidly it is for your object.
I think you missed what sharding is about. If your application needs to update a counter object many times a second you get collision problems. The sharding is about splitting the updates to parallel transaction on partial-counter objects. Not on using multiple counter objects in ONE transaction. 2009/10/21 Ori <[email protected]>: > > I've got this simple model, which consists several properties (like > 3-4), and several counters (about 5-6) > a. The counters are being updated rapidly > b. I need them to be updated in one transaction (to be persistent, > avoid collisions and unexpected behavior) > > I saw the article about shraded counters, and I was wondering if it > will make any affect using them when this entity is being updated with > one transaction ? > > Thanks, > Ori. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
