speaker-diarization icon indicating copy to clipboard operation
speaker-diarization copied to clipboard

Published 20 hours ago • verified publisher icon aalto-speech

Excessive CPU

Open chrisspen opened this issue 5 years ago • 1 comments

I'm not sure if this is a bug, but I tried running the docker diarization example on a 1 hour audio containing 4 speakers. The spk-diarization2.py script ran for 3 hours consuming 100% of my CPU, and still hadn't completed, so I had to kill the container and abort the evaluation. Is that normal performance or should it have completed in that time?

I've tested other diarization tools on the same file, and they normally complete in about 1/4 of the file's length, or about 15 minutes for a 1 hour long file.

chrisspen avatar Sep 20 '19 18:09 chrisspen

I'm not sure if this is a bug, but I tried running the docker diarization example on a 1 hour audio containing 4 speakers. The spk-diarization2.py script ran for 3 hours consuming 100% of my CPU, and still hadn't completed, so I had to kill the container and abort the evaluation. Is that normal performance or should it have completed in that time?

I've tested other diarization tools on the same file, and they normally complete in about 1/4 of the file's length, or about 15 minutes for a 1 hour long file.

Hey which diarization tool did you use for a 1 hour long file.

milind-soni avatar Sep 01 '21 08:09 milind-soni