Refactor: Isolate concurrency for local vs. remote transcription approaches
Open
Nobody has claimed this yet.
priority/minor
- Dominant language
- Python
- Stars
- 589
- Forks
- 76
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Background
Currently, a single lock is used for both local and remote transcription models in the voice recognition agent. This may unnecessarily limit throughput for remote transcription calls that don't require the same locking mechanism as local models.
Discussion Points
- Separate concurrency logic for local vs. remote transcription flows
- Improve throughput for remote transcription calls
- Maintain thread safety for local model usage
References
- Originally discussed in PR: https://github.com/RobotecAI/rai/pull/357
- Specific comment: https://github.com/RobotecAI/rai/pull/357#discussion_r1928635284
Next Steps
- Design a solution that handles concurrency appropriately for both local and remote transcription approaches
- Implement separate flows while maintaining code maintainability
- Measure and compare throughput improvements
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.
Assessment
This issue has not been assessed yet.