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
Is your feature request related to a problem? Please describe.
Sort of, Tdarr tends to be a resource hog. When other applications use NVENC encoding while Tdarr is using NVEC, performance suffers on those other applications (notably Plex). Setting Low FFmpeg/HandBrake process priority to on tends to help this issue.
Describe the solution you'd like
Couple possible solutions: When non-Tdarr processes are detected on the node, the node should either:
A. Turn on Low FFmpeg/HandBrake process priority for that node or,
B. Stop all processes on the node entirely until the other processes have completed.
This could be accomplished by querying processes on a schedule with a package similar to ps-node or simple event listeners.
Describe alternatives you've considered
This could easily be done with scripting and a cron job, but as far as I'm aware Tdarr doesn't have a cli that would make this possible.
Additional context
Slow transition times between low and normal process priority could still cause issues for other applications.
The text was updated successfully, but these errors were encountered:
kage1414
changed the title
Set node to low process priority when using NVENC and other NVENC processes are detected on the gpu.
Set gpu node to low process priority when non-tdarr NVENC processes are detected.
Nov 4, 2021
It wouldn't be possible to instantly stop the node entirely (not in a simple cross-platform way ) but in 2.00.13 you could run a script which sets low CPU priority whenever you like (don't run on 2.00.12 or below):
Is your feature request related to a problem? Please describe.
Sort of, Tdarr tends to be a resource hog. When other applications use NVENC encoding while Tdarr is using NVEC, performance suffers on those other applications (notably Plex). Setting Low FFmpeg/HandBrake process priority to on tends to help this issue.
Describe the solution you'd like
Couple possible solutions: When non-Tdarr processes are detected on the node, the node should either:
This could be accomplished by querying processes on a schedule with a package similar to ps-node or simple event listeners.
Describe alternatives you've considered
This could easily be done with scripting and a cron job, but as far as I'm aware Tdarr doesn't have a cli that would make this possible.
Additional context
Slow transition times between low and normal process priority could still cause issues for other applications.
The text was updated successfully, but these errors were encountered: