ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
RocksDB column families let you give hot sessions and cold audit logs different compaction and compression policies inside one database. A worked C++ example plus verification and pitfalls.
RocksDB write stalls come from exactly three backlogs: unflushed memtables, L0 file accumulation, or pending compaction bytes. Here's how to tell them apart and fix the right one.
Compaction strategy is a data-lifecycle decision, not a tuning knob. How TWCS windows work for time-series, where out-of-order writes break them, and how to verify.
Meta's continuous profiling pipeline ingests custom trace events with high-cardinality dimensions such as request IDs and user segments. The documented architecture uses a columnar storage backend derived from Gorilla principles with label deduplication and compaction, but public materials do not characterize how compaction latency behaves when label cardina
The goal is to select a value for the `rate_limiter_bytes_per_sec` option that prevents foreground write stalls caused by uncontrolled compaction while keeping compaction latency within acceptable bounds for workloads that vary in intensity over time. Because RocksDB does not provide auto‑tuning for the limiter and the setting applies globally across all col
cassandra
facebook
rocksdb