slow running in arm about fast-ctc-decode HOT 2 CLOSED

I haven’t benchmarked on arm myself but the differences you are reporting are much larger than I would expect. Is possible that you are using a debug build on arm and release build on x86? make test will result in debug build, can you rebuild and benchmark again after doing make clean && make build.

Thank you very much, I rebuilt the package with make clean && make build and got a wheel file named target/wheels/fast_ctc_decode-0.2.5-cp37-cp37m-manylinux1_aarch64.whl. I use pip3 install target/wheels/fast_ctc_decode-0.2.5-cp37-cp37m-manylinux1_aarch64.whl and got fast_ctc_decode-0.2.5-cp37-cp37m-manylinux1_aarch64.whl is not a supported wheel on this platform. error. After renamed the file to fast_ctc_decode-0.2.5-cp37-cp37m-linux_aarch64.whl, I installed the package successfully. And the new benchmark on arm:

beam search length of 1000 for 1000 times cost: 1.6493666172027588s, mean: 0.0016493666172027588
viterbi search length of 1000 for 1000 times cost: 0.06065034866333008s, mean: 6.065034866333008e-05

The time differences are small, thanks a lot.

from fast-ctc-decode.

I haven’t benchmarked on arm myself but the differences you are reporting are much larger than I would expect. Is possible that you are using a debug build on arm and release build on x86? make test will result in debug build, can you rebuild and benchmark again after doing make clean && make build.

from fast-ctc-decode.