jerry-024 commented on PR #711: URL: https://github.com/apache/paimon-rust/pull/711#issuecomment-5311487614
One remaining latency gap is worth covering in this PR: `RangeIoStats` records amplification counters, but not the wall time spent waiting for range reads. The blocking `pread -> read_ranges -> runtime.spawn -> sync_channel::recv` path is therefore folded into `native_search_wall_ms`, so remote-storage wait cannot be separated from native search work. Could we add a shared `AtomicU64` such as `range_read_wait_nanos` and accumulate the duration around `recv()`? The name should avoid claiming this is pure I/O time: it also includes runtime scheduling, the internal range-read permit queue, and result delivery. This would partially cover the missing range-read permit signal as well. The Lumina/full-file fallback paths can remain follow-up work, and the non-batch path is outside this PR's stated scope. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
