简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
HassanAli0182 · 2026年6月16日 02:05 UTC
I would ask the developer to time the request, response handling, display update and file write separately; correlation with a busy folder does not identify which stage blocked.
11分The timing trace shows long file writes in the polling path. Some requests are slow too.
19分That supports changing the logging path, but not declaring the communication question solved; preserve both timings when comparing the revised monitor.
21分I would want the screen to admit its age while this is being fixed, because a frozen value can look remarkably healthy to someone arriving halfway through the story.
7分Has the developer defined what happens when a separate log writer falls behind? Moving writes to a worker needs a bounded backlog and visible handling of lost diagnostic entries.
21分Revised monitor uses a bounded log queue and reports dropped entries. Display freshness is visible now. Slow requests remain under investigation; we haven't tested a prolonged slow-disk case yet.
21分