missed your comment... this is what we're doing, except we avoid the 1MB limitation by storing the data sets in blobs and store the pointer to the blob in the entity record
On Wednesday, November 13, 2013 1:20:21 PM UTC-6, Kaan Soral wrote: > > A single datastore entity can hold up to 1MB's > > How big will a single dataset be? > > If it's smaller than 1MB's in summarized format, you could build a queue > based solution to handle the >15/s data rate > > You could also probably develop something like a tree, with each entity > representing a node and storing the data about the leafs etc, it could > maybe lead up to a practical median calculator, just an idea, the point is: > > as Vinny P stated, the solution is always based on exactly what you are > doing > > On Tuesday, November 12, 2013 10:07:34 PM UTC+2, Mathieu Simard 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? >> > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
