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

[BUG] Neon performs worse than C #1088

Closed
hanyin-arm opened this issue Dec 19, 2024 · 1 comment
Closed

[BUG] Neon performs worse than C #1088

hanyin-arm opened this issue Dec 19, 2024 · 1 comment

Comments

@hanyin-arm
Copy link

Hi, when we build and run your hello-neon sample app on my Pixel 2 (Snapdragon 835) and Pixel 9 (Tensor G4), both show a worse performance using Neon as shown below

image
image

Upon some initial investigation, our SIMD experts are worried about this sample code's FIR filter's Neon algorithm being sub-optimal, thus not leveraging Neon's potentials on performance boost.

Please let us know your thoughts and we can follow up either in public or private (e.g. via my @arm.com email)
Thank you and happy holidays 🎄

@hanyin-arm hanyin-arm changed the title [BUG] Neon approach performs worse than C approach [BUG] Neon performs worse than C Dec 19, 2024
@DanAlbert
Copy link
Member

That sample was actually rewritten last year but is still waiting for review from a team member with more experience in vectorization. You can see the PR here: #1067.

Upon some initial investigation, our SIMD experts are worried about this sample code's FIR filter's Neon algorithm being sub-optimal

Yeah, that doesn't surprise me at all. The whole sample will be removed once the new one merges though :)

@DanAlbert DanAlbert closed this as not planned Won't fix, can't repro, duplicate, stale Jan 7, 2025
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

2 participants