Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jellyscrub stops using hardware acceleration mid-extraction #88

Open
BrunoJurkovic opened this issue Feb 23, 2023 · 2 comments
Open

Jellyscrub stops using hardware acceleration mid-extraction #88

BrunoJurkovic opened this issue Feb 23, 2023 · 2 comments

Comments

@BrunoJurkovic
Copy link

Hey there,

after checking out the new update with hardware acceleration, I've noticed that a few minutes after starting the task, hardware acceleration is no longer being used, validated by checking nvidia-smi during the task, and by checking resource usage.

When starting the task, nvidia-smi output:

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1629      G   /usr/lib/xorg/Xorg                 80MiB |
|    0   N/A  N/A      1925      G   /usr/bin/gnome-shell               56MiB |
|    0   N/A  N/A   3961253      C   ...ib/jellyfin-ffmpeg/ffmpeg      125MiB |
+-----------------------------------------------------------------------------+

After a few minutes (10 in my case):

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1629      G   /usr/lib/xorg/Xorg                 80MiB |
|    0   N/A  N/A      1925      G   /usr/bin/gnome-shell               56MiB |
+-----------------------------------------------------------------------------+

Any other logs you want attached @nicknsy ?

@nicknsy
Copy link
Owner

nicknsy commented Feb 23, 2023

Jellyscrub logs everytime a bif file is generated. Do the logs indicate that a bif file was attempted with hw accel but when you check it isn't actually using it?

I'd think it's more likely that you have a common decode profile like HEVC 10 unchecked, so most of the generation is done without hw accel.

@GS059
Copy link

GS059 commented Jul 20, 2023

did you try checking again after a few seconds?
I noticed if you refresh in-between file generation you can catch it without a process showing, but if you refresh again it show back up.

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

No branches or pull requests

3 participants