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
Hi I am trying the speaker-diarization pipelines to detect speaker numbers, and I noticed that it can be very cpu hungry and each time I run it it creates a lot of processes and I can see many many processes in htop. My saw that there is the num_workers param that can control the processes used, but only when we call the classes like Segmentation, VAD etc...
I checked the code and the wrappers seems very deep and I didn't see where I can specify the num_workers param. Anyone has any idea about it? Any advice is appreciated!
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
-
Hi I am trying the speaker-diarization pipelines to detect speaker numbers, and I noticed that it can be very cpu hungry and each time I run it it creates a lot of processes and I can see many many processes in
htop
. My saw that there is the num_workers param that can control the processes used, but only when we call the classes like Segmentation, VAD etc...here is how I use the model.
I checked the code and the wrappers seems very deep and I didn't see where I can specify the num_workers param. Anyone has any idea about it? Any advice is appreciated!
Beta Was this translation helpful? Give feedback.
All reactions