-
Notifications
You must be signed in to change notification settings - Fork 19
waveshaper: Avoid allocations while resampling #287
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
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for you contribution!
I need a bit more time to review and verify it in full, but I left a few first remarks. Could you have a look?
If you wish, you could add a benchmark to benches/my_benchmark.rs
to see if it actually outperforms the previous version (it will run in the CI and post a comment on your PR).
Benchmarking is not helpful here. The allocation might only cause issues very rarely but in fatal ways. Same applies to mutexes. Lock-free code is often less performant on average than locking. |
|
Fair point! Although I'm reasonably sure I have merged your updated code. Thanks again |
Fixes #143.