pub struct Stats {
pub requests: u64,
pub reads: u64,
pub wanted: u64,
pub read: u64,
}Expand description
What the pool has done, for the byte counting spec/engine/13-measurement.md section 13.5
asks for.
The distinction between Self::wanted and Self::read is the one that matters and it is
the reason coalescing is counted rather than assumed harmless. A merged read that spans a gap
reads bytes nobody asked for, and a reader whose pruning is wrong reads bytes it should have
skipped. Both show up here as a ratio and neither shows up in the answer.
Fields§
§requests: u64How many requests were submitted.
reads: u64How many physical reads those requests turned into.
wanted: u64How many bytes the requests asked for.
read: u64How many bytes were actually read off the device.
Trait Implementations§
impl Copy for Stats
impl Eq for Stats
impl StructuralPartialEq for Stats
Auto Trait Implementations§
impl Freeze for Stats
impl RefUnwindSafe for Stats
impl Send for Stats
impl Sync for Stats
impl Unpin for Stats
impl UnsafeUnpin for Stats
impl UnwindSafe for Stats
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more