-
Notifications
You must be signed in to change notification settings - Fork 293
Arm performance issue #4151
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
Can you convert the script into an executable with https://github.com/vercel/pkg and see how the timing looks like |
I will try it later. |
Anybody has access to raspberry pi 3 please try to reproduce this issue |
It seems there has been no activity on this issue for a while, and it is being closed in 30 days. If you believe this issue should remain open, please leave a comment. |
It seems there has been no activity on this issue for a while, and it is being closed. If you believe this issue should remain open, please leave a comment. |
Details
I encountered some performance slowdowns in Node.js 18.16 while developing for IOT devices.
To reproduce the problem, I wrote a simple prime number generation program:
C version, compiled with
gcc -o prime prime1.c -O2 -lm
(all test platforms were 64-bit)JS version
JS version is almost as fast as C counterpart on Raspberry Pi 4B (overclocked, 2.0GHz)
Running the same programs on Intel N4200, A72, and A76 CPUs yielded similar results.
However, JS version took nearly twice as much time as C version to execute on Raspberry Pi 3B+:
Same occurence was found on Rk3399 (2 A73 and 4 A53 cores, 4GB RAM):
as well as Rk3588S (4 A75 and 4 A55 cores, 16GB RAM):
and also on RK3308 (rockpi-s):
I would like to know what caused this slowdown as well as how to optimize performance for A53 CPUs. Many thanks!
Node.js version
Example code
No response
Operating system
Scope
Performance on Arm A53, A55, and A35 CPUs
Module and version
Not applicable.
The text was updated successfully, but these errors were encountered: