time-series-database

Tag

Cards List
#time-series-database

@Greptime: Repartitioning a big table is normally a migration project: new table, dual-write, backfill TB of history, cut over. Gr…

X AI KOLs Timeline · 2026-07-14 Cached

GreptimeDB v1.1 introduces online repartitioning for existing tables via a single ALTER TABLE statement, eliminating the need for data migration, dual-writes, or application changes. It leverages shared object storage and logical shards to update manifests and routing without moving data between nodes.

0 favorites 0 likes
#time-series-database

@Greptime: trace_id is high-cardinality — so Xiaomi's smart factory team didn't reach for an inverted index. They put a Bloom skip…

X AI KOLs Following · 2026-06-23 Cached

Xiaomi's smart factory replaced Loki with GreptimeDB for log storage, handling billions of rows per month with tailored indexing: Bloom skipping for high-cardinality trace_id, inverted index for low-cardinality fields, and fulltext search on message bodies.

0 favorites 0 likes
#time-series-database

@Greptime: We refreshed our deep-dive on Mito2, the storage engine inside GreptimeDB. LSM-tree write path. Columnar Parquet SSTs. …

X AI KOLs Following · 2026-06-22 Cached

GreptimeDB's Mito2 storage engine uses an LSM-tree design with columnar Parquet SSTs, three-level scan pruning, and TWCS compaction. The blog post provides a full walkthrough of its architecture.

0 favorites 0 likes
#time-series-database

@Greptime: On Prometheus remote write, the bottleneck wasn't network or memtable — it was the Region Worker holding &mut while dec…

X AI KOLs Following · 2026-06-02 Cached

GreptimeDB v1.0 introduces Pending Rows Batcher, a three-stage pipeline that moves CPU-intensive work off the Datanode's critical section, improving Prometheus remote write throughput from 1.20M to 2.17M points/sec and reducing Datanode CPU usage by 20%.

0 favorites 0 likes
← Back to home

Submit Feedback