From 3d8f8ee8e51050b09b410cc351bc9ec79c51eb0d Mon Sep 17 00:00:00 2001 From: LinuxServer-CI Date: Thu, 4 Dec 2025 20:50:32 +0000 Subject: [PATCH] Bot Updating Documentation --- docs/images/docker-baseimage-selkies.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/images/docker-baseimage-selkies.md b/docs/images/docker-baseimage-selkies.md index a44eb18fb9..9f50dd64c6 100644 --- a/docs/images/docker-baseimage-selkies.md +++ b/docs/images/docker-baseimage-selkies.md @@ -252,6 +252,21 @@ curl -X POST http://localhost:8083/tokens \ Clients in this mode must connect with a valid token (`?token=...`) to establish a WebSocket connection. +### All GPU Acceleration - use sane resolutions + +When using 3d acceleration via Nvidia DRM or DRI3 it is important to clamp the virtual display to a reasonable max resolution. This can be achieved with the environment setting: + +* `-e MAX_RESOLUTION=3840x2160` + +This will set the total virtual framebuffer to 4K, you can also set a manual resolution to achieve this. +By default the virtual monitor in the session is 16K to support large monitors and dual display configurations. Leaving it this large has no impact on CPU based performance but costs GPU memory usage and memory bandwidth when leveraging one for acceleration. If you have performance issues in an accelerated session, try clamping the resolution to 1080p and work up from there: + +``` +-e SELKIES_MANUAL_WIDTH=1920 +-e SELKIES_MANUAL_HEIGHT=1080 +-e MAX_RESOLUTION=1920x1080 +``` + ### DRI3 GPU Acceleration For accelerated apps or games, render devices can be mounted into the container and leveraged by applications using: