⚡ Bolt: Optimize clock updates to reduce idle CPU wakeups - #69
Conversation
- Replaced 1000ms `setInterval` with a self-adjusting `setTimeout` in `ui.ts` to sync clock updates exactly with minute boundaries. - Reduces main thread wakeups by 98.3% for the clock component, saving CPU cycles and improving idle battery life. - Added a 50ms buffer to the calculation to prevent premature firing before the minute rolls over. - Updated unit tests to correctly advance fake timers by the new dynamic delay. - Logged optimization pattern in `.jules/bolt.md`. Co-authored-by: raythurman2386 <36676341+raythurman2386@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
This PR implements a performance optimization for the clock UI component.
💡 What
The clock updating mechanism in
ui.tswas refactored to use a dynamic, self-adjustingsetTimeoutinstead of a staticsetInterval(..., 1000). The new logic calculates the exact milliseconds remaining until the next minute boundary (plus a 50ms buffer) and schedules the next update accordingly.🎯 Why
Previously, the clock was waking up the main thread 60 times a minute, evaluating
timeStr !== lastTimeStr, and modifying the DOM exactly once. Waking up the CPU every 1 second just to check if a minute has passed is a classic battery drain on laptops for dashboard apps.📊 Impact
This reduces main thread wakeups for the clock component by 98.3% (from 60 per minute to 1 per minute), lowering idle CPU usage and extending battery life without any loss in visual responsiveness.
🔬 Measurement
All formatting, linting, and 74 unit tests pass successfully. The
ui.test.tswas updated to verify the dynamicsetTimeoutprogression correctly.PR created automatically by Jules for task 1355081994415740217 started by @raythurman2386