OOM when using VAD #1193
Comments
Purfview
added a commit
to Purfview/faster-whisper
that referenced
this issue
Dec 10, 2024
Reported problems: SYSTRAN#1193 SYSTRAN#1169 VAD implementations consumes humongous memory amounts [original Silero doesn't have this problem] This PR should fix the OOM problem. Alt solution could be removing 'lru_cache'.
|
Try this fix -> #1198 |
|
I still have to run some tests, but I tried it and it looks promising. The latest commit has fixed it. Thank you @Purfview! I will let you know if the issue persists. |
MahmoudAshraf97
pushed a commit
to Purfview/faster-whisper
that referenced
this issue
Dec 12, 2024
Reported problems: SYSTRAN#1193 SYSTRAN#1169 VAD implementations consumes humongous memory amounts [original Silero doesn't have this problem] This PR should fix the OOM problem. Alt solution could be removing 'lru_cache'.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, does somebody else experience issues with memory consumption when transcribing audio files containing a lot of speech (~ 4 hours long)? I am running the latest version of faster-whisper in a Kubernetes pod on a g4dn AWS instance. The server has 4 cores, 1 GPU, and 16GB RAM, but the pod is limited to 2 cores. The base image is
pytorch/pytorch:2.5.1-cuda12.4-cudnn9-runtimeand as per this pinned issue the installed versions should be compatible:The process gets killed during the transcription phase when VAD is enabled. I tried the solution described here, but it doesn't help. See the logs attached. Anyone has any idea what could be the cause of the OOM?
libraries.txt
logs on sigkill.txt
The text was updated successfully, but these errors were encountered: