mirror of
https://github.com/XRPLF/rippled.git
synced 2026-07-30 18:40:28 +00:00
7da5ac5992
nudb_bytes was documented as a NuDB file size, one place even claiming a filesystem stat. It observes Database::getStoreSize(), which sums the object payloads this process has written. It excludes NuDB's keys, bucket padding and log, and resets with the process. node_written_bytes calls the same accessor, so the two series are equal by construction and a write-amplification ratio built from them is a constant 1.0. Neither Backend nor Database exposes a file-size accessor, so nothing reports on-disk size today. The Ledger Data & Sync panel plotting node_reads_hit / node_reads_total was titled "NuDB Cache Hit Ratio" and described as reads served from cache. fetchHitCount_ increments whenever a fetch returned an object, whatever served it, so the ratio is a found rate. It reads near 100% while every fetch goes to disk, which made the cold-read failure mode look impossible. Renamed to "NuDB Read Found Ratio" and rewrote the guidance to pair it with read latency. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>