pub struct Retention {
pub depth: usize,
pub release_when_idle: bool,
}Expand description
How long a shared dataflow keeps what a subscriber might still ask for.
docs/26-arrangement-sharing-report.md
§26.9 recorded both of these as constants that should have been policies: the history was 64
versions “because a subscriber further behind than that is not the bottleneck”, and the
arrangements were never dropped at all.
Fields§
§depth: usizeThe ceiling on retained change history, in versions. The reader frontiers are the floor, and they are usually far lower — this bounds what one subscriber that has stopped rendering can pin.
release_when_idle: boolWhether to give up the arrangements when the last subscriber goes.
On, the process holds nothing between fanouts and the next subscriber pays a cold start. Off,
they stay warm for a reconnection that may not come. The trade is a real one and it belongs
to a deployment rather than to this file, which is why it is here and not a const.