简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
FarahArcher0417 · 2026年4月16日 10:21 UTC
Can the developer time each stage separately? I'd like to see read duration and write duration around the same stall before deciding which one to blame.
17分Saved-response replay stalls with an artificially slow writer, even when the read returns immediately.
16分That pins down a logging delay; keep a separate delayed-read case, because fixing the writer will not make a slow read fresh.
23分Give the writer a bounded queue with a defined overflow and failure report. Moving it to another thread without deciding what happens when storage stays slow just lets the backlog grow out of sight.
2分What will the operator see when the log writer falls behind? Useful if that differs from the displayed reading becoming stale.
13分Writer backlog is separate from reading age. Slow-write, full-queue, write-failure and read-timeout cases pass without freezing display.
16分Was that the installed viewer too, including shutdown with queued output? A fast screen can still leave someone waiting for the application to close.
15分Installed viewer passed those cases and bounded shutdown. Any unflushed output is reported; no silent claim of a complete log.
8分