FarahArcher0417 · 16 Apr 2026, 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 pointsSaved-response replay stalls with an artificially slow writer, even when the read returns immediately.
16 pointsThat pins down a logging delay; keep a separate delayed-read case, because fixing the writer will not make a slow read fresh.
23 pointsGive 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 pointsWhat will the operator see when the log writer falls behind? Useful if that differs from the displayed reading becoming stale.
13 pointsWriter backlog is separate from reading age. Slow-write, full-queue, write-failure and read-timeout cases pass without freezing display.
16 pointsWas that the installed viewer too, including shutdown with queued output? A fast screen can still leave someone waiting for the application to close.
15 pointsInstalled viewer passed those cases and bounded shutdown. Any unflushed output is reported; no silent claim of a complete log.
8 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.