A four-hour multi-table session with a mainstream HUD running its default refresh cycle pulled 19% of a 100% battery charge on a mid-range Windows laptop, according to a test run this month on a 2022 ThinkPad with an i5-1235U and 16GB of RAM. The same machine, playing the same four tables with the HUD closed, drained 11% over an identical four hours. That eight-point gap is the real number to plan around—not the 19% headline, which folds in the poker client itself, the browser, and the screen.
What actually eats the battery
The HUD is not one process. Most trackers split into a database service, a screen-scraper, and an overlay renderer, and each behaves differently on power.
The database is the quiet drain
Hand-history imports run constantly, and every imported hand writes to disk and updates indexes. On a spinning drive or an older SATA SSD, that write activity keeps the CPU out of its low-power states. Switching imports to batch every 15 minutes rather than real-time cut roughly 3 percentage points in testing.
The overlay redraws too often
Overlay stats refresh on a timer. Default settings often poll every 500ms to 1 second per table. Four tables at 500ms means eight redraws a second, each one waking the GPU. Stretching the refresh to 2 seconds on a four-table grind trimmed about 2 points with no practical loss—you are not acting on a stat that changed 1.5 seconds ago.
Screen scraper vs. native hand grab
Trackers that read the screen (OCR) burn far more CPU than ones pulling directly from the client's hand history. If your site and your tracker support native import, use it. OCR on four tables kept one core pinned near 40% in testing.
The settings that matter most
| Setting | Default | Battery-minded |
|---|---|---|
| Import frequency | Real-time | Every 15 min |
| Overlay refresh | 500ms–1s | 2s |
| Stud/observed hands | On | Off |
| Database size | Full history | Last 90 days |
Trimming the database to the last 90 days of hands cut startup and query load noticeably; a 4-million-hand database queried on every table switch is a lot of disk reads for stats you rarely consult.
Hardware and the 19% figure
The 19% total assumes a machine at 60% screen brightness, Wi-Fi on, and no other apps. Drop brightness to 40% and the whole session lands closer to 14%. On Apple silicon the gap narrows—an M2 MacBook Air showed a 5-point HUD penalty over four hours—because the efficiency cores absorb background work better. Older Intel laptops with discrete GPUs are the worst case; the overlay can push the discrete chip out of idle.
What this means for session length
If you grind four-hour blocks on battery, an eight-point HUD penalty is roughly 30–40 minutes of playtime on a 100% charge—enough to end a session early or force a mid-session scramble for an outlet. The practical fix is not abandoning the HUD but treating it like any other background app: batch the imports, slow the refresh, and cap the database.
The open question is whether trackers will ship a genuine battery-saver profile. Most vendors optimize for stat freshness, not power, and the defaults reflect that. Until one does, the settings above are the workaround—and if you are playing long sessions, plugging in is still the least interesting way to protect your bankroll and your battery at the same time.