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

Switch to a faster thread-safe FIFO - std::sync::mpsc is showing up in profiling as a bottleneck. #116

Open
mitchmindtree opened this issue Apr 16, 2018 · 0 comments

Comments

@mitchmindtree
Copy link
Member

mitchmindtree commented Apr 16, 2018

Currently the mpsc::SyncSender used to send audio monitoring data back to the GUI thread is showing up as a clear bottleneck. The profiling suggests that there's some inner lock contention going on that is causing delays that even exceed the cost of the FFT calculations. It might be worth looking into the crossbeam lock-free queues to solve this.

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