Do you really need all detailed data? Consider to store aggregated data by means of sharded or non-sharded counters instead:
http://code.google.com/intl/es/appengine/articles/sharding_counters.html http://blog.appenginefan.com/2009/10/non-sharded-counters-part-2-using-task.html -aah On 18 dic, 19:25, killer barney <[email protected]> wrote: > So here's a problem that I'm having a lot of trouble with. > > I want to keep track of the statistical breakdown of my users who > insert an entity in a certain table of mine. (Kind of like google > analytics, when a user visits a webpage, how many are using browsers > X, how many stay for how long, etc) How should I go about this? On > every insert, should I list out all of the user's data into the entity > and then have a cron job that goes and collects and calculates all the > data so that it can store it in a culmultive property? It doesn't seem > like a very scalable idea. What if I keep adding more stats, that > table just gets bigger and bigger. > > In a relational database, it seems pretty easy. Just join and the > count. Anyone have any ideas on the datastore? -- 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.
