I might also suggest using a 'materialized' view. Store the computed values in a datastore entity that you can fetch by key-name (perhaps using the day as the key-name). You can easily extend this logic for weeks, months, and years. Even if you only store each day's stats as an entity fetching an entire year is easy, just generate the key-names and do a batch fetch. Furthermore, the key-name strategy works well with memcache.
It is also very easy to recompute / update a given day's values with the pre-computed view technique. One downside to the blobstore is that you can't change / update an existing 'file,' so corrections might be trickier. Robert On Fri, May 20, 2011 at 00:14, PF <[email protected]> wrote: > There is 1MB limit for memcache. I can imagine when I'd like to show > statistic chart for last year there could be the need for more amount of > data then 1MB so I cannot use memcache. Also for such 1 year statistic it is > pretty enough to be recalculated only once per week e.g. Putting data to > memcache for one week is not so ideal from my point of view. > > No other way then memcache? Or are my arguments above not relevant? > > Thx, > Peter > > -- > 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. > -- 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.
