BenBarnes0544 · 16 Jun 2026, 07:33 UTC
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 pointsDeveloper found writes inside the update callback. Request durations have not been compared yet.
24 pointsThat identifies where writes happen, not how much delay they caused. Measure the duration too.
22 pointsAnd 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 pointsDoes the trend require every sample, or may the display show only the latest? Different loss policies.
5 pointsThat is undecided. I'll separate the trend requirement from display freshness in the review, thanks Anika.
20 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.