That's one possibility I haven't considered. Since we just need to provide the stats of the past 24 hours, it doesn't need to be very up-to-date.
And in the greater scheme of things, we can probably afford to lose a few event counts. So this certainly points to saving this to memcache and uses task queue to periodically update the datastore as a good enough solution that won't break the bank :) Thanks for the suggestion! On Mon, Apr 9, 2012 at 5:42 PM, Jeff Schnitzer <[email protected]> wrote: ... > Another solution is to use memcache increment() and periodically sync > diffs to the datastore. This is less reliable but much cheaper. A > variation on this is to use a backend instead of memcache. > > Unless each customer downloads more than one thing per second, you > won't need to shard the customer "number of things" downloaded number. > So that's not too unreasonable. And even if you do get a burst, you > can push the actual count update to the task queue so it won't hurt > the UX. The # will just lag a little. > > Jeff -- 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.
