pub const SNAPSHOT_MAX_WAIT_MS: u64 = 50;Expand description
…and the shortest time it will keep trying, in milliseconds. An attempt is cheap, so on an oversubscribed machine the count can run out while the reader has merely been off-CPU; the deadline is what distinguishes “the writer is relentless” from “I was not scheduled”. Measured on a 2-core box with three load tests and a spawned writer running at once: count alone gave up on about 1 read in 60 000, this gives up on none.