Alexey Zhiltsov

sending above 1M points/sec is hitting a limit on the receiver. Both carbon-c-relay and go-carbon barely cope with it via one connection. Multiple connections is the easiest way to fix...

config parameter, defaulted to 1?

We have faced the issue when under high load/high event rate it corrupts metrics. Normally we have around 170K points a second per relay, but during the burst we had...

The disk write will be linear, so even spinning disk should handle it fine.

@jjneely did you have any spare cycles for review by any chance?

@dolvany we had 12 carbon-cache processes per host with carbon-c-relay on the same host on front of them in order to distribute the load. At certain point it stopped work...

There was already one #15 and I would also prefer to have it. Might be an extra parameter at invocation will be a good compromise solution?

> what are the downsides to carbonserver compared to our current cluster method? do we lose any functionality or desirable characteristics? Carbonserver has nothing to do with clusters. It just...

Most of statsd implementations can't provide you a redundant distributed aggregations, the only one I know which give a such promise is https://github.com/avito-tech/bioyino Another pain point is a lack of...

> but absense of good alternative relay worrying me more. @deniszh, We are currently working on the new relay, check it out: https://github.com/bookingcom/nanotube