Performance Regression in Whisper models when timestamp generation is enabled
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4.7k
- Forks
- 536
- Avg merge
- 12h 12m
- Merged PRs (30d)
- 4
Description
Hello
Several reports mention that WER improves greatly when adding <|notimestamps|> to the initial prompt in whisper decoding aka disabling timestamps generation, I tested this using This and This. You can check https://github.com/mobiusml/faster-whisper/pull/18#issuecomment-2196788100 for an example of decoding difference using the same encoder output
There are several other reports including but not limited to:
https://github.com/SYSTRAN/faster-whisper/discussions/1010
https://github.com/SYSTRAN/faster-whisper/issues/985
Also generation with timestamps has a lower toks/s and the slowdown increases when increasing the batch size
on the side, we have several PRs waiting for @trungkienbkhn review but he seems to be out of office, it'd be great if one of his colleagues has any information when he might return
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with benchmark/wer_benchmark.py and benchmark/evaluate_yt_commons.py, then compare Whisper decoding with and without timestamp generation. Check the linked reports and decoding example for differences in WER and tokens per second, especially as batch size increases. The issue does not name a CTranslate2 source file or test, and its acceptance criteria remain unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- machine-learning, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100