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

Server/Client scenario degradation Versus "all-in-one? #110

Open
EricVee68 opened this issue Jan 23, 2024 · 1 comment
Open

Server/Client scenario degradation Versus "all-in-one? #110

EricVee68 opened this issue Jan 23, 2024 · 1 comment

Comments

@EricVee68
Copy link

Forgive my inquiry if this has already been discussed...
Does the overhead of implementing this server/client/web sockets scenario show degradation in overall "real-time" consumption/transcribe/translation/display performance compared to a solution that contains all functionality in one script base?
This solution is terrific, but for "single client" needs, is this overkill and potentially slower?

@zoq
Copy link
Contributor

zoq commented Jan 27, 2024

Hello, if you run everything locally the extra latency is negligible (maximum 10ms), most of the latency is consumed by the actual transcription process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants