Hacker News Reader

We run OpenTSDB (which stores its data in Apache HBase) at scale.

150m-200m events/minute and about 20-30 trillion (10^12) events stored. Doubling about every 12-18 months or so.

While it's true that things start to creak at scale, this has worked remarkably well for us so far. I doubt M3DB is somehow magical in this regard.

View on HN

M3DB ingested 30 million datapoints per second (so 1.8 billion per minute) with each node writing hundreds of thousands of writes per second. The dataset was in the petabytes.

For us the cost savings vs OpenTSDB (millions of dollars of hardware), the faster query time and the reduction in oncall overhead was worthwhile.

Hundreds of thousands per second isn't very high when you compare that to clickhouse or kdb+.

Reply on news.ycombinator.com