简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Cannot blame the FR10 connection while our log writes stall

IsaacBrooks0868 · 2025年9月20日 21:38 UTC

已关闭
IS
IsaacBrooks0868
I want to locate the delay before changing the network. Our read-only FR10 display freezes when detailed logging writes to the shared folder, then catches up. Cell controls are separate. The programmer suspects file writes, but we have no timing around the request itself.

6 条回复

SA
SarahBrown0937

Time the request, the processing and the file write separately, with the timing capture kept away from the same slow writer, so the measurement does not disappear into the delay you are investigating.

22
IS
IsaacBrooks0868

Programmer added separate timings. In the captured freeze, the request returned before a long file write. We will compare more than this one occurrence before changing the display.

16
SA
SarahBrown0937

Have the programmer review a bounded logging queue and an explicit policy for a full queue or failed writer, because moving the writes elsewhere without a limit can simply move the eventual stall.

16
AN
AnilAli0201

Does the frozen screen still show the old reading as current?

6
SA
SarahBrown0937

Isaac, Anil's display-age question belongs in the change as well, especially if delayed logs and delayed readings can now occur independently.

20
IS
IsaacBrooks0868

Anil, yes, it did. The proposed display shows reading age and logging health separately. Sarah, the queue limit and overflow behaviour are in review; the revised writer has not been installed yet.

1

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .