You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All % are effective CPU usage. The CPU has 4 cores, so 400% would be loading all 4 cores at 100%. CPU values are going up and down around the values, so only approximated values here. Observed with htop via OpenSSH connection.
Idle (with Engine just sitting on the initial Source screen after bootup): ~7% CPU usage by Engine (572 MB total RAM usage by everything running on OS)
htop seems to report CPU 0 peaking to ~20% sometimes with no hint in the process list for why. Some kernel thing?
Plugging in a disk on the source screen: short ~68% peak (576 MB)
One source is mounted and sitting on library screen: quick 80% spike, then dropping off to ~9% (588 MB)
Scrolling through tracks in the library screen: ~45% (594 MB)
Scrolling through the left side tabs: ~90% with load mostly on CPU 1 (601 MB)
At this point I wanted to isolate playback stats, so I rebooted the player and went straight to loading tracks:
Playing 1 FLAC track (3:12 min long): 70~80%, mostly loading CPU 1 (617 MB)
one Engine thread continuously in D (I/O busy) state as it plays the track
Idle after playing a track: 60~70%
Playing 2 FLAC tracks (6:09 min long + the first track): 90~110% (647 MB)
Playing 3 FLAC tracks (6:41 min long + the other two tracks): ~140% (668 MB)
Playing 4 FLAC tracks (7:36 min long + the other three tracks): ~190% (685 MB)
It seems that the audio engine does not do anything until the first track is played, from there on it continuously uses a chunk of the available CPU resources. CPU load depends highly on amount of tracks loaded and playing.
I'll report on stressloading the CPU and its effects once I get to it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
All % are effective CPU usage. The CPU has 4 cores, so 400% would be loading all 4 cores at 100%. CPU values are going up and down around the values, so only approximated values here. Observed with htop via OpenSSH connection.
At this point I wanted to isolate playback stats, so I rebooted the player and went straight to loading tracks:
D
(I/O busy) state as it plays the trackIt seems that the audio engine does not do anything until the first track is played, from there on it continuously uses a chunk of the available CPU resources. CPU load depends highly on amount of tracks loaded and playing.
I'll report on stressloading the CPU and its effects once I get to it.
Beta Was this translation helpful? Give feedback.
All reactions