Our status window stops updating during big log writes, then catches up. Is there a cheap check before IT blames the network?
fr5 status freezes when the log saves
LiamArcher0403 · 2025年11月28日 07:06 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
6 条回复
Ask when the timestamps are made. Our log stamps entries after the file operation, which makes it poor evidence of what waited before the write. Do you have separate read and display timings?
6分No. Just the saved-file times. The screen clock freezes too.
5分Then don't call that a connection outage yet. A saved-input replay with a slow writer could show whether the application freezes without a network involved. The developer should time the stages independently of the writer being tested.
17分David's replay is the check I'd ask for. Also have them show what a genuinely old reading looks like; a frozen green box is not a useful status description.
-5分And include the case where writing fails completely. Otherwise they may repair the delay and leave the screen looking happy while the log has stopped saving anything.
4分Developer has the replay request. Slow writer and failed writer both included. No result back yet.
3分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .