(3.4.120 was an unpublished release candidate of this change; 3.4.121 is the
released version.)
Fixed
- The display board no longer burns CPU (or GPU) to move the photo rail.
A profiling pass on real kiosk hardware (a Raspberry Pi 4 driving a wall
TV 24/7) found the hybrid layout pinning two CPU cores around the clock
and running the chip at 63–67 °C. Two causes, fixed in two rounds. First,
the rail's slow scroll was a JavaScript animation loop rewriting the
column's position sixty times a second — invisible on a desktop,
saturating on a Pi; replacing it with a browser-native animation halved
the main-thread cost on the same hardware. But re-measuring showed the
GPU compositor still working continuously — anything in constant motion
costs a new frame sixty times a second no matter how the motion is
produced, and recompositing a tall column of photos every frame is real
work on a Pi's graphics core. So the rail no longer glides at all: it
advances one card at a time — a half-second slide every eight
seconds, then completely still — which also reads better from across a
room (the eye isn't tracking a crawling target). Between steps the page
is fully idle: zero animation-frame callbacks, zero per-frame style
writes, no motion for the compositor to composite. The rebuild also
halves the number of photos the rail keeps in memory. Card order still
holds steady for a full rotation before refreshing to the current
closest, and everything else — radar, polling cadence, photos — was
measured healthy and left alone. If you run the board on a Pi, this
release is the difference between a hot kiosk and a mostly idle one.