8 Commits

Include renames

Author	SHA1	Message	Date
Nils Andreas Svee	743a050416	fix(stats): align rolling directional loss with window counts	2026-10-04 12:20:47 +07:00
Nils Andreas Svee	f2fce2f330	refactor(irtt-client): move cadence into managed runner	2026-10-02 00:31:17 +07:00
Nils Andreas Svee	b6043e4961	refactor(stats): use shared measurement statistics	2026-09-27 00:03:35 +07:00
Nils Andreas Svee	db9bd515bb	refactor(stats): retain exact finite timing samples ... `SampleMode::Exact` retained exact samples for eight of the eleven public timing metrics. Send call, timer error, and server processing always built their `TimeMetric` with retention disabled, so a finite run reported no median for them even though they are the same public `TimeStats` type and appear in the same summary table with a Median column. Derive one `retain_exact` decision from the sample mode in `CoreStats::new` and apply it to every timing metric, so exact mode means the same thing for all of them. Running-only mode is unchanged and still retains none of them. The retention estimator counted eight exact sample streams per measurable reply. Rename it to the eleven exact samples an ordinary successful probe can retain and document the wider optional-measurement upper bound, which raises the finite estimate on this target from 668 to 764 bytes per probe. A test counts the metrics a fully measured probe actually retains and compares it against that constant, so retention and its estimate cannot drift apart unnoticed. No new median-capability type was needed: `TimeStats::median_ns` already distinguishes a retained median from an absent one, and an optional measurement the server never supplied still produces no samples at all.	2026-08-15 10:41:17 +07:00
Nils Andreas Svee	b93e6d0ab7	refactor(stats): own retention memory estimates	2026-08-15 10:25:04 +07:00
Nils Andreas Svee	e0dec9ac5f	refactor(stats): make late-reply sampling explicit ... The TUI suppressed late-reply timing by rebuilding the event with sent_at, rtt, server_timing, one_way and received_stats erased. That leaked stats policy into event construction and, as a side effect, reclassified a matched late reply as an untracked late reply. StatsConfig now carries an explicit LateReplyMode. Measure keeps today's behavior for every existing caller. CountOnly keeps the reply a late unique reply and keeps packet, byte and late counters updating, while suppressing timing, one-way, server-processing and IPDV contributions and reporting contributed_sample == false. Cumulative and rolling snapshots share the policy. Genuinely untracked late replies stay untracked in both modes. The TUI selects CountOnly and passes the original event straight to the collector.	2026-08-15 01:17:46 +07:00
Nils Andreas Svee	bec56d4114	refactor(client): use SignedDuration for effective RTT to support negative values ... Simplify RttSample by merging signed and unsigned fields into a single SignedDuration for adjusted and effective RTT. This ensures accurate reporting and statistics when server processing time exceeds raw RTT.	2026-05-17 21:30:51 +07:00
Nils Andreas Svee	19e0e7aab9	refactor(irtt-stats): extract core aggregation module	2026-05-13 14:57:19 +07:00