node.js 100% cpu utilization when running StatsD

Question

I've wanted to test StatsD perfromance with some stress test which I've made. Eventually I found out that when there are something like 80,000 packets per sec the Node.js is getting to 100% cpu utilization on my environment.

I know that 80,000 event per sec is quite huge amount of events , but I wonder if anyone knows what are the limits of StatsD in regarding to Node.js. What is a normal events rate?

Also, is there something I can do to imporve Node.js performance so it won't get to 100% cpu utilization?

Answer 1

According to a StatsD contributer, the metrics rate which was tested and measured was between 15,000 - 20,000 metrics per sec. Thats quite good enough and it is what I was looking for.

You can see more details about it in the issue I've opened at StatsD's github project: https://github.com/etsy/statsd/issues/249