How do I fix ClickHouse "Too many parts"?
TOO_MANY_PARTS means too many small inserts, not too much data. Batch your writes, turn on async inserts, and stop over-partitioning your MergeTree tables.
#configuration#performance#troubleshooting
Articles
page 4 / 13
TOO_MANY_PARTS means too many small inserts, not too much data. Batch your writes, turn on async inserts, and stop over-partitioning your MergeTree tables.
#configuration#performance#troubleshooting
A table-by-table workflow for tuning existing SQL Server indexes: find unused and overlapping indexes, merge them, and replace blanket rebuilds with statistics updates.
#db-administration#indexing#maintenance
Writes fail and reads still work. Understand Redis eviction policies, find what's filling memory, and pick the right fix depending on whether Redis is a cache or a datastore.
#caching#configuration#nosql
A founder's guide to choosing PostgreSQL or MySQL: team experience, managed hosting, scaling paths, extensions, licensing, switching cost, and a clear "pick PostgreSQL unless" rule.
#db-administration#scalability#schema-design
timestamptz doesn't store a time zone, and timestamp silently drops the offset you pass in. What each type really stores, where timestamp causes bugs and the one case where it's right.
#data-types#schema-design
Side-by-side SQL for the differences web developers hit daily: quoting, case sensitivity, identity columns, RETURNING, upserts, booleans, JSON, GROUP BY, full-text search, migrations and time zones.
#data-types#migrations#orm
A session doing nothing can stop VACUUM from cleaning every table and stall your next migration. Find them, kill them safely and prevent them with the right timeouts.
#maintenance#mvcc#transactions
How to choose between PostgreSQL, MySQL, SQLite and MongoDB for a web app, where Redis and a search engine fit, a decision table by app type, and when the PostgreSQL default is wrong.
#data-modeling#scalability#schema-design
The old UUID performance problem came from UUIDv4's randomness, not UUIDs themselves. How UUIDv7 changes the trade-off, what the extra 8 bytes still cost and when to pick each.
#data-types#indexing#schema-design
Explains by mechanism where InnoDB or PostgreSQL does less work for lookups, updates, joins, connections and replication, then shows how to benchmark your own workload with pgbench and sysbench.
#internals#mvcc#performance
Page 1 takes 5 ms and page 5,000 takes 4 seconds. OFFSET reads and throws away every skipped row. Switch to keyset (cursor) pagination for constant-time pages.
#indexing#pagination#performance
A reference comparison of PostgreSQL and MySQL: storage and MVCC, isolation defaults, DDL, data types, indexes, replication, licensing and tooling, with a decision summary.
#indexing#internals#replication