Blog - Hyperbyte Cloud

Blog

A collection of 9 posts

From 99 million to 1.9 million: what an ingest benchmark doesn't tell you

analytics Featured

From 99 million to 1.9 million: what an ingest benchmark doesn't tell you

We measured an embedded ClickHouse inserting ~99 million rows/second. Then we put a real database in front of it — a network endpoint, line/msgpack parsing, a durable write-ahead log, series indexing — and ran a ramp test on the same machine. It ingests ~1.9 million points/second at the

Scaling chDB inserts from 5 million to 99 million rows/second

Scaling chDB inserts from 5 million to 99 million rows/second

How an embedded ClickHouse — running in-process, not as a server — scales its write path with a connection pool, and how far that actually goes when you give it real cores. chDB is ClickHouse compiled into a library. There's no server, no socket, no network round-trip: you link libchdb.

Your Old Data Isn't a Migration Blocker: Exporting Historical Time-Series from InfluxDB v1 to HyperbyteDB

Most migration guides cover updating Telegraf, Grafana, and your scripts. But historical data—months or years of it—gets left behind with no clear path forward. Here's how to export that data from InfluxDB v1 and load it into HyperbyteDB.

The InfluxDB v1 Migration Checklist: Which Clients Just Need a URL Change

Most migration posts focus on one client. The reality is InfluxDB v1 stacks have Telegraf, Grafana, custom apps, and scripts. Here's the client-by-client migration checklist that tells you which integrations just need a URL change and which need adjustment.

What InfluxDB v1 OSS Actually Costs You (And How HyperbyteDB Changes the Equation)

InfluxDB OSS is a great starting point—until you need retention policies, high availability, or replication. Here's the hidden cost of those features and how HyperbyteDB includes them by default.

Keep Your Telegraf Configs. Add Master-Master Replication. No Sales Call Required.

InfluxDB charges enterprise pricing for replication. HyperbyteDB includes master-master clustering in the open-source binary. Here's what that means for your Telegraf setups and why teams are making the swap without a single config change on the client side.

Before you trust our numbers, run this.

Benchmark numbers mean nothing without context. Here's how to run HyperbyteDB's own ingestion benchmarks, what each stage actually measures, and the environment metadata you need before comparing anything.

InfluxDB v1 Compatibility in HyperbyteDB: What Works, What Doesn't, and Why

How HyperbyteDB's InfluxDB v1 compatibility works end-to-end: line protocol, /write, /query, InfluxQL, Prometheus metrics—and where things diverge.

One URL to Drop In: InfluxDB v1 Compatibility in HyperbyteDB

Our strongest signal for product-market fit isn't a benchmark or a feature list—it's that teams drop in HyperbyteDB by changing one URL in their existing Telegraf configs. Here's what we validated and what to watch.