Skip to content

Conversation

@m1k1o
Copy link
Owner

@m1k1o m1k1o commented Sep 16, 2025

Spinoff of #531 hopefully fixing CPU resources issue and upgrading to the latest stable version.

Node 18 is not on trixie, fair point, we need to upgrade to 22.

@m1k1o
Copy link
Owner Author

m1k1o commented Sep 17, 2025

CPU resoruces difference, exactly the same video played in bullseye (left) and trixie (right):

image

Bullseye:

  • GStreamer 1.22.0
  • Chromium 134.0.6998.35 built on Debian GNU/Linux 12 (bookworm)

Video & audio was played flawlessly.

Trixie:

  • GStreamer 1.26.2
  • Chromium 140.0.7339.127 built on Debian GNU/Linux 13 (trixie)

Video was missing a lot of frames, audio was played flawlessly.


Maybe something changed in gstreamer?

@h-town
Copy link

h-town commented Oct 4, 2025

IIRC Trixie marks the first release wherein Debian defaults to both Wayland and Pipewire regardless of WM/DE. Possible there exist components used for migration (e.g. PA -> PW) or default configs (e.g. for GStreamer) changing to recognize that fact between Bookworm and Trixie (or in this case even longer)? Also does this same relative CPU uplift occur between base images as well or only when certain components of neko stack are introduced?

@jameskitt616
Copy link

What about 1:1 comparing how much each service consumes with htop in the docker container, so it's possible to see which service requires more CPU?

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.

4 participants