Replies: 1 comment
-
Perhaps it is specifically the fault of this particular Docker image, or rather the Alpine Linux versions of which differ? Objectively, version v22 is faster than v16. You can always use Bun, but this may be considered sabotage (https://bun.sh/) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I want to upgrade my project from Node v16.19.1 to Node 22.13.1, before upgrading I did a benchmark to measure performance changes after the upgrade (http server)
But I got a bad result. The performance of Node V22 has a significant decline compared to Node V16 (specifically referring to http scenarios)
Below is the environment and results of my test. I hope you can get your answers. Thank you.
Docker run node v22.13.1 alpine(3.20) on centos7(8cpu 16G)
Docker run node v16.19.1 alpine(3.12) on centos7(8cpu 16G)
Docker run script (The contents in the docker image are basically the same)
create app.js content
run
Throughput testing using abtest.
# n = 1000 or 2000 ab -n 100000 -c n http://localhost:30256/
# n = 1000 or 2000 ab -n 100000 -c n http://localhost:30255/
Test Result
I've tested it many times and the results are basically the same.
Can anyone tell me the reason or a more standard test method.
From the perspective of resource consumption, the Node V22 memory usage is smaller, but the CPU has reached a peak of 100% during the test.
Thank for everyone
Beta Was this translation helpful? Give feedback.
All reactions