IOSurface Display
Chau7 sends frames from GPU memory directly to the display. No compositor. No extra copy. No wasted frame.
What is IOSurface Display in Chau7?
IOSurface Display is a rendering feature in the Chau7 terminal that writes Metal render passes directly to an IOSurface-backed texture. The macOS display controller reads the finished frame straight from GPU memory, bypassing the WindowServer compositor entirely.
Standard macOS applications render into a backing store that the WindowServer compositor then blits into the final display framebuffer. This introduces an extra GPU-to-GPU copy and at least one frame of latency. Chau7 eliminates both by using IOSurface as the shared memory surface between the Metal render pass and the display hardware.
How Chau7 reduces compositor latency on macOS
Chau7's Metal render pass writes the terminal frame into an IOSurface-backed texture. The CALayer backing the terminal view is configured with the same IOSurface, so the display controller reads the finished frame directly from GPU memory. The result is a zero-copy path from the Metal render pass to photons on screen.
This architecture is particularly beneficial on high-refresh-rate displays. On 120Hz ProMotion displays, every millisecond counts. By removing the compositor blit, Chau7 reclaims roughly 1 to 2 milliseconds per frame, keeping total render latency under the 8.3ms budget required for 120fps output.
How does Chau7's IOSurface display compare to other terminals?
Most macOS terminals render into a standard backing store that the WindowServer compositor then copies to the display framebuffer. iTerm2, Alacritty, and Kitty all go through this compositor path, adding an extra GPU blit and at least one frame of latency to every rendered frame.
Chau7 is the only terminal that renders directly to an IOSurface, removing the intermediate copy. This zero-copy approach saves 1 to 2 milliseconds per frame, which is the difference between hitting and missing the 8.3ms frame budget on a 120Hz display.
Does IOSurface bypass require special entitlements?
No. IOSurface is a public framework available to all sandboxed macOS applications. Chau7 uses the standard CALayerBackedIOSurface approach that Apple documents for high-performance rendering.
No special entitlements, private APIs, or elevated permissions are needed. Chau7's IOSurface integration works within the standard macOS application sandbox.
Does IOSurface display affect window transparency or vibrancy?
Chau7's IOSurface display is fully compatible with macOS vibrancy and transparency effects. The IOSurface participates in the compositor blending stack normally.
The difference is that Chau7 writes directly to the surface rather than going through an intermediate backing store. Transparency, blur, and vibrancy effects are applied by the compositor during blending, which happens after Chau7 has written the frame to the IOSurface.
Why IOSurface display matters
The macOS compositor adds a full frame of latency and a GPU-to-GPU copy for every window. For a terminal where you notice every millisecond of input lag, that is unacceptable overhead.
Chau7's IOSurface display lets rendered frames travel directly from GPU memory to the display hardware. Zero extra copies. Zero extra latency. For developers who care about input responsiveness, Chau7's zero-copy rendering path makes a measurable difference.
Questions this answers
- What is IOSurface Display in Chau7 terminal?
- How does Chau7's IOSurface display compare to other terminals?
- How to reduce compositor latency in a macOS application
- Does IOSurface bypass require special entitlements?
- Does this affect window transparency or vibrancy effects?
Frequently asked questions
What is IOSurface Display in Chau7 terminal?
IOSurface Display is a rendering feature in the Chau7 terminal that writes Metal render passes directly to an IOSurface-backed texture. The macOS display controller reads the finished frame straight from GPU memory, bypassing the WindowServer compositor. This zero-copy path eliminates an extra GPU blit and removes roughly one frame of latency.
How does Chau7's IOSurface display compare to other terminals?
Most macOS terminals render into a standard backing store that the WindowServer compositor then copies to the display framebuffer. iTerm2, Alacritty, and Kitty all go through this compositor path. Chau7 is the only terminal that renders directly to an IOSurface, removing the intermediate copy and saving 1-2ms per frame.
How to reduce compositor latency in a macOS application
Chau7 reduces compositor latency by rendering into an IOSurface-backed Metal texture and configuring the CALayer to use the same IOSurface. The display controller reads the finished frame directly from GPU memory without an intermediate compositor blit. This approach saves 1-2ms per frame and keeps Chau7 under the 8.3ms budget for 120fps on ProMotion displays.
Does IOSurface bypass require special entitlements?
No. IOSurface is a public framework available to all sandboxed macOS applications. Chau7 uses the standard CALayerBackedIOSurface approach that Apple documents for high-performance rendering. No special entitlements or private APIs are needed.
Does this affect window transparency or vibrancy effects?
IOSurface display in Chau7 is compatible with macOS vibrancy and transparency. The surface participates in the compositor blending stack normally. The difference is that Chau7 writes directly to the surface rather than going through an intermediate backing store.