LEDMatrix

rick/LEDMatrix

Fork 0

mirror of https://github.com/ChuckBuilds/LEDMatrix.git synced 2026-10-05 06:45:09 +00:00

Files

T

History

ChuckandClaude Opus 5.5 1252df9bad perf(timing): say which render-thread work a late frame followed

The soak already says how often a moving frame reached the panel late, but
not what the render thread was doing just before it. Vegas does two kinds of
work there between frames -- building its strip (compose, extend) and, with
live elements, patching changed pixels into it -- and deciding whether either
is affordable needs their own numbers.

- FrameTimingRecorder.note_op(kind, nbytes) tags the next presented frame.
  Totals gain op_frames, late_op_frames, op_freezes and op_bytes per kind;
  aggregate() still takes frames without ops. The file schema is unchanged.
- Vegas tags compose and every strip extension (with the bytes it copied).
- frame_soak prints an "after work" table: frames, late %, freezes and MB
  moved per kind, only when something tagged its work.
- render_bench gains --strip-screens (Vegas-sized strips), --patch-bytes /
  --patch-every / --patch-where (in-place column writes, as a live element
  update does) and --extend-every-screens / --extend-width (append + trim on
  a fixed cadence that holds the strip's width).

No runtime behaviour changes: this is the measurement gate for live Vegas
elements.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-30 18:36:38 -04:00

__init__.py

fix(display): Vegas teardown and 240s default; remove dead Vegas buffer code (#637 )

2026-09-24 17:37:15 -04:00

config.py

feat(vegas): render plugin content off the render thread, and keep it off the GIL when the panel needs it (#630 )

2026-09-24 19:57:03 -04:00

coordinator.py

feat(display): systemd watchdog and heartbeat for a frozen render loop (#687 )

2026-09-30 11:15:31 -04:00

geometry.py

fix(display): Vegas teardown and 240s default; remove dead Vegas buffer code (#637 )