sof
sof copied to clipboard
thesofproject
Audio: aec: optimize acoustic echo cancellation processing
This check-in introduces performance optimization modifications to the audio Echo Cancellation (AEC) implementation. The enhancements primarily focus on refining loop structures and memory copy operations to ensure more efficient use of cycles.
@ShriramShastry could you please explain in simple terms what exactly you're trying to optimise in this PR - which algorithms you find non-optimal, how you replace them, and - very importantly - how you test the result? Can you provide a single simple example like "I take this kind of a loop and replace it with this and this brings X% performance gain?"
Sorry but google is going to NACK this until we at least get a release and stabilize this component first
Sorry but google is going to NACK this until we at least get a release and stabilize this component first
Okay, we'll wait till the release and stable component are available.
@ShriramShastry could you please explain in simple terms what exactly you're trying to optimise in this PR - which algorithms you find non-optimal, how you replace them, and - very importantly - how you test the result? Can you provide a single simple example like "I take this kind of a loop and replace it with this and this brings X% performance gain?"
Sure, The initial test measurements are taken per loop. The results are positive. @yongzhi1 , could you kindly help with the current updates and communicate the information here?
Thank you
Sorry but google is going to NACK this until we at least get a release and stabilize this component first
Okay, we'll wait till the release and stable component are available.
Pushing it out to v2.10 to allow stabilization, baseline MCPS measurements and alignment.
Sorry but google is going to NACK this until we at least get a release and stabilize this component first
Okay, we'll wait till the release and stable component are available.
Thanks :) just remember, premature optimization is the root of all evil
Sorry but google is going to NACK this until we at least get a release and stabilize this component first
Okay, we'll wait till the release and stable component are available.
Thanks :) just remember, premature optimization is the root of all evil
Do you have any progress ? Thanks