Dave, Once again, thanks for taking the time to reply. Really appreciate the thought. I think I will remove the sharded counters in favor of a count directly on the objects I'm working with. And then adjust the model later if necessary.
I guess I saw so much disucusssion of sharded counters here that I thought they were the right choice. It's not clear to me what exactly "high write contention" actually is, i.e. how many writes per minute/ second you'd have to hit to have write conflicts, i.e. when you should consider a sharded approach. Cheers, Beast On Dec 27, 5:01 am, "David Symonds" <dsymo...@gmail.com> wrote: > On Sat, Dec 27, 2008 at 8:24 AM, newb <pcbeas...@gmail.com> wrote: > > I'm wondering how a product like Digg works (even though they're not > > on GAE). They have counters for each of their articles which would > > have high write contention. But they somehow manage to keep their > > articles sorted by count as well. The model I'm shooting for has some > > similar characteristics. > > I really don't think Digg would have very much write contention *per > story*. Popular stories getting thousands of diggs usually do so over > the course of a day or more, so it's really only a few writes per > minute. Now if they were doing a write to a single object for every > single digg, that would be high write contention. > > I'd suggest just implementing it the simplest way you can see, and try it. > > Dave. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
