On Wed, Nov 13, 2013 at 7:58 PM, Mathieu Simard <[email protected]> wrote:
> Here's a better definition of the problem: > I receive a *value* for a tracked metric (i.e. start-up time) for > different systems at a rate of 15/s. > This rate is expected to grow quickly as clients add systems. > I need to produce a rolling median of that metric. > At the same time, I'm trying to keep the cost low since volume is only > going to grow. > > A few months back someone posted a similar problem to this mailing list: a mobile game needed a backend to collect scores from thousands of mobile clients, compute a leaderboard, then send back the leaderboard to the clients, all in a 10 second window. After the discussion, the consensus IIRC was to either (1) run App Engine backends to reap incoming requests and calculate values within a high-memory backend, or (2) run a Compute Engine machine to reap and calculate values. The choice is up to you since it depends on what you're comfortable with, but if low cost is an important goal I'd choose the Compute Engine route. Since your application and values can be held entirely within RAM, you can choose a high-memory, diskless instance to optimize your resource usage. However if the incoming values will have spiky traffic levels or if your application requires complex services such as Endpoints, hosting on App Engine is the better solution. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- 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.
