Skip to content

Reduce display buffer memory usage - #781

Open
Samueltgg12 wants to merge 3 commits into
techomancer:mainfrom
Samueltgg12:perf/memory-and-ram
Open

Samueltgg12 wants to merge 3 commits into
techomancer:mainfrom
Samueltgg12:perf/memory-and-ram

Conversation

@Samueltgg12

Copy link
Copy Markdown
Contributor

Summary

  • Start shared framebuffer and readback buffers at 1024 rows, growing only to the active high-water mark.
  • Allocate Newport auxiliary/DID planes and software compositor, debug-overlay, and capture buffers on demand.
  • Size every direct framebuffer/readback writer explicitly, including GR2, IMPACT, InfiniteReality, VPro, and O2.
  • Add focused sizing tests and update the architecture/changelog notes.

Memory impact

  • The base Rex3Screen allocation drops from 52 MiB to 16 MiB per head.
  • Newport adds only its 1024-row auxiliary and DID planes when refreshed.
  • The software compositor, debug overlay, and iris-gui GL capture no longer reserve 2048 rows up front.

Validation

  • Tested by the requester: build and tests passed.
  • git diff --check was clean before commit.
  • I did not run additional builds or tests, per request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant