Our diagnostic display pauses during heavy log activity. Separate from cell controls. Which timings distinguish file-write delay from communication delay?
How can I tell whether verbose FR10 logging delayed the screen?
BenBarnes0544 · 16 Jun 2026, 07:33 UTC
6 replies
Replying to BenBarnes0544
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.
15pointsReplying to AishaBell0692
Developer found writes inside the update callback. Request durations have not been compared yet.
24pointsReplying to BenBarnes0544
That identifies where writes happen, not how much delay they caused. Measure the duration too.
22pointsReplying to BenBarnes0544
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.
-2pointsReplying to AishaBell0692
Does the trend require every sample, or may the display show only the latest? Different loss policies.
5pointsReplying to AnikaBaker0508
That is undecided. I'll separate the trend requirement from display freshness in the review, thanks Anika.
20pointsAdd to the discussion
Welcome to Application Robot
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.