-
-
Notifications
You must be signed in to change notification settings - Fork 11k
BUG: Possible regression in CPU supported features for aarch64 #22257
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
Comments
@seiko2plus Thoughts? |
@seiko2plus thoughts? |
Compile time detection of edit: fix pr url |
The data that's being used is a personal user's documents and their contents, and I don't have access to anything running aarch64 at the moment. I'll see what I can wrangle up anyway, but it's probably going to take some time to make a minified code sample using something. |
I'm not familiar with |
My apologies, it has taken me a while to free up my Pi 3 from other things to be able to test this and boil it all down. At least with the public dataset for multi-label classification I found and a Pi, I haven't been able to reproduce any sort of slowdown. Either this requires a certain amount of data or data types which I can't easily produce, or it's something specific to the ROCKPI. Unless @pedrom34 is able to provide more information, this can probably be closed. |
Uh oh!
There was an error while loading. Please reload this page.
Describe the issue:
While investigating paperless-ngx/paperless-ngx/issues/1364, it was noticed between
numpy==1.22.3
andnumpy==1.23.1
, the supported SIMD extensions reported bynumpy.show_config()
changed, with1.23.1
not finding the ASIMDFHM feature.The device is a ROCK64, with a Cortex A53, Armv8, which I believe should have all th features implied by ASIMDFHM (basing on the list here).
I thought #21749 would fix this, but the issue persists with 1.23.2
Reproduce the code example:
Error message:
1.22.3 Config
1.23.1 Config
NumPy/Python version information:
numpy==1.23.1 / numpy==1.23.2
Context for the issue:
The training of some classifiers goes from a few minutes, to never completing.
The text was updated successfully, but these errors were encountered: