Our FR10 monitoring screen began stalling after detailed logging was enabled. The log folder is busy during the pauses. How can I separate file-write delays from slow replies without changing the independent cell controls?
How can I tell whether logging is freezing my display?
Eli_Bailey · 2025年5月29日 03:50 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
6 条回复
回复 Eli_Bailey
Measure the read, processing and file-write times separately. Then compare a recorded input replay with and without the extra logging. That should show where the display waits.
19分The replay pauses too. File writes run on the same thread as the screen updates, and their durations line up with the stalls. Network replies are absent from that test.
19分回复 Eli_Bailey
Have the developer move those writes away from the display work, with a bounded queue and a clear response when logging cannot keep up. Avoid an endlessly growing backlog.
16分回复 Eli_Bailey
Will the screen still show when its displayed reading is old?
3分It needs that too. The current display freezes its value without making the age obvious. I've added the stale-reading state to the review.
8分The revised replay keeps the screen responsive and reports delayed logging under an overloaded test. Stale readings are labelled. Live communication timing still needs checking before we close the issue.
15分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .