How can I tell whether verbose FR10 logging delayed the screen?

BenBarnes0544 · 2026年6月16日 07:33 UTC

回复讨论

主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文

BE
BenBarnes0544
Our diagnostic display pauses during heavy log activity. Separate from cell controls. Which timings distinguish file-write delay from communication delay?

6 条回复

AI
AishaBell0692

We once had the screen blamed when the delay occurred before its update was even queued. I'd ask the developer to time request, receive, processing, writing and display stages on the same occurrence.

15分
BE
BenBarnes0544

Developer found writes inside the update callback. Request durations have not been compared yet.

24分
AN
AnikaBaker0508

That identifies where writes happen, not how much delay they caused. Measure the duration too.

22分
AI
AishaBell0692

And ask what the intended user sees when updates age. While the timing work continues, an old status should not remain indistinguishable from a fresh reading.

-2分
AN
AnikaBaker0508

Does the trend require every sample, or may the display show only the latest? Different loss policies.

5分
BE
BenBarnes0544

That is undecided. I'll separate the trend requirement from display freshness in the review, thanks Anika.

20分

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 和 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。