Adds "bytes_released" and "bytes_flush_requested", representing total bytes released from disk as a result of segment release (as allocation bytes + overhead - not counting unused "waste"), resp. total size we've requested flush callbacks to release data, also counted as actual used bytes in segments we request be made released. These counters, together with bytes_written, should in ideal use cases be at an equilibrium (actually equal), thus observing them should give an idea on whether we are imbalanced in managing to release bytes in same rate as they are allocated (i.e. transaction rate).
104 KiB
104 KiB