nextcloud / nextcloud/stt_whisper2
cpu_threads left at default, meaning 4 threads?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- run the app
- observe only 4 of your cores being used
- 🤷
Expected behaviour
"The app will hog all cores by default" according to the docs
Actual behaviour
it uses 4
(rest of the template not really relevant)
https://github.com/nextcloud/stt_whisper2/blob/main/lib/main.py#L63C20-L63C58 initialises the Model(s) with default parameters, which for cpu_threads is 0, but apparently that actually means 4(?)
see https://github.com/SYSTRAN/faster-whisper/blob/d3bfd0a305eb9d97c08047c82149c1998cc90fcb/faster_whisper/transcribe.py#L619
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 at lib/main.py line 63, where Model is initialized with default parameters, then compare the cpu_threads handling in faster-whisper's transcribe.py around line 619. Reproduce the four-core behavior and verify what a default value of 0 means; document the expected default behavior and the change needed to make the application match it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100