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
Blog 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.
Blog Run InfluxDB v1 on Kubernetes? Swap the Operator, Keep the URLs. Your InfluxDB v1 Kubernetes stack is already half the battle—Helm charts, StatefulSets, monitoring, alerting. HyperbyteDB's operator drops in as a replacement. Same InfluxDB v1 API endpoints, same client configs, same Grafana dashboards.
Blog Your Telegraf + Grafana + Alerts Stack, Now on a Database That Doesn't Buckle Point Telegraf and Grafana at a different URL and keep the rest of your observability stack. What transfers unchanged, where InfluxQL behaviour differs, and what ships in the open-source binary.
Blog Why InfluxDB Enterprise Pricing Hits a Wall Retention policies, continuous queries and replication all sit behind InfluxDB's paid tier. What that actually costs you, what high availability means for telemetry, and what ships in HyperbyteDB's open-source binary.
Blog Every Sensor, Every Tick: InfluxQL Analytics on IoT Data at Scale Millions of IoT sensors sending high-frequency data. Real-time dashboards querying across thousands of devices. This is where InfluxDB v1 starts to buckle—and where HyperbyteDB runs without compromise.
Blog Stop Watching Your Metrics Explode: High Cardinality Without the Rewrite InfluxDB v1 crawls when cardinality hits the roof. HyperbyteDB handles it with columnar storage and ClickHouse—same InfluxQL, no rewrite, no OOM. Here's how.
influxdb 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.
Blog 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.
Blog 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 InfluxDB v1 Compatibility in HyperbyteDB: What Works, What Doesn't, and How to Cut Over HyperbyteDB speaks InfluxDB v1 line protocol and InfluxQL on the same endpoints. The precise version: endpoint coverage, InfluxQL support, the known differences, benchmark numbers and what to watch when cutting over.
