This seems like a bad idea, you could just add it as a pull-queue task, instances can die pretty easily
You also assumed that the data is small enough to process/store easily, however this doesn't seem to be the case On Friday, November 15, 2013 9:04:58 PM UTC+2, Stephen wrote: > > > On Tue, Nov 12, 2013 at 8:07 PM, Mathieu Simard > <[email protected]<javascript:> > > wrote: > >> Since there is no appengine solution available such as the Redis atomic >> list, I'm left wondering how to implement a cost effective rolling median. >> Has anyone come up with a solution that would be more convenient than >> running a redis instance on Google Compute Engine? >> > > - batch data in front-end instance memory > - flush data to a pull queue every time window > - run a task every time window to gather all data batches from pull queue > - merge data, compute moving median, write result to data store > > Instances will be started as more data is submitted. Tune the frequency > of the calculation so that the size of the pending data batches does not > overwhelm a single task. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
