March 28, 2011 - by jacksonwest
Over on his blog, Dave Pacheco sets up a test case that uses the analytics visualization tools baked into our Node.js Cloud Services to diagnose the source of a latency-inducing garbage collection problem:
A few weeks ago I posted about Cloud Analytics on no.de. I described the various metrics we included in the initial launch and how they’re relevant for Node applications. Today I’ve got a small example using HTTP request latency and garbage collection. I wrote a small HTTP server in Node.js that simply echoes all requests, but in doing so deliberately creates a bunch of garbage. That is, it allocates a bunch of extra memory while processing each request but doesn’t save it anywhere. The goal is just to observe garbage collection in action..