Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor: Isolate concurrency for local vs. remote transcription approaches #384

Open
coderabbitai bot opened this issue Jan 24, 2025 · 0 comments
Open
Assignees

Comments

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 24, 2025

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

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant