Haydex: Engineering Journey to 178.6 Billion Rows Per Second Database Performance
This is the story of how we turned a failed filter prototype into a production system running at 178.6B rows/sec in 30 days.
Read the full articleYou might also wanna read
Why Engineers Are Ditching Redis and RabbitMQ for Plain Postgres in 2026
A growing counter-movement in software development is challenging the long-accepted practice of combining Postgres, Redis, and RabbitMQ in a
Debugging a slow password reset query in CockroachDB: from 700k rows to 10
It all started one morning. I opened Slack as usual to start my working day, only to find a message from the CTO
gaultier.github.io·16d ago
Memory as the New Bottleneck: How Data Engineers Can Cope with Rising Storage Costs in the AI Era
How Pandas chunking, Dask, and Polars help process millions of records when adding more compute isn't an option.
towardsdatascience.com·14d agoSimulating Database Performance Under Load with Speedscale
Big data storage tools like BigQuery, Hadoop, and Cassandra are used to manage large volumes of structured and unstructured data generated b
How a missing ANALYZE call turned a seconds-long SQL insert into a 25-minute freeze
A developer building a star-schema data warehouse on PostgreSQL using the Brazilian Olist e-commerce dataset found that loading 112,647 rows
Iterating terabyte-sized ClickHouse® tables in production
Schema migrations on a streaming ClickHouse table? At 100s of MB/s? Here's how we do it across clusters without losing a single bit.
Comments
Sign in to join the conversation.
No comments yet. Be the first.