1 Test Environment1.1 Server HardwareThe host to be tested is AWS cloud server. Two tests are selected 1.1.1 t2.microt2.micro is an EC2 with breakthrough performance, which is the server in AWS global free package. The configuration is as follows: t2.micro is an EC2 with breakthrough performance, which is the server in AWS global free package. The configuration is as follows:
Single core 1G, CPU performance is 0.45ECU, and can reach 2ECU when performance is improved. The network performance is said to be 20Mbps~100Mbps PS: EC2 Compute Unit (ECU) – One EC2 Compute Unit (ECU) is equivalent to the computing power of a 1.0-1.2 GHz 2007 Opteron or 2007 Xeon CPU. 1.1.2 c5.largeThen we selected a c5.large for evaluation.
Dual-core 4G, performance can reach 9ECU 1.1.3 PressThe press machine is another c5.large in the same availability zone. 1.2 Testing Tools1.2.1 Test terminalThe ab tool is mainly used for testing. The ab tool can run up to 200 million concurrently, which is sufficient for single-machine testing. For the use of ab tools, please refer to another blog: https://www.jb51.net/article/231502.htm 1.2.2 Server MonitoringThe server-side monitoring mainly uses the AWS backend cloudwatch service, and the CPU and memory usage are checked in the top tool. For the use of top command, please refer to another blog: 1.3 Test MethodAdd a test route directly in the express framework app.js and return res.end() directly. 2 Test Data2.1 c5.largeWe can see from the figure that when the concurrency is 2000, the average response time is 874.725ms, and the QPS is around 2286.43. On a 2-core 4G server with more than 300/month, the performance of the express framework itself is not bad. 2.2 t2.microWe can see from the figure that when the concurrency is 300, the average response time is 189.191ms, the QPS is around 1585.7, and the performance of T2 at 70 blocks/month is quite good. However, it can also be seen from the figure that after the concurrency reaches 1000, the overall performance is not very stable. 3 Related DocumentsBlog on estimating the concurrent volume of IoT devices: https://www.jb51.net/article/231516.htm Stress testing tool ab: https://www.jb51.net/article/231502.htm Indicators and methods of stress testing: https://www.jb51.net/article/231518.htm The above is the editor's introduction to using node+Express to test server performance. I hope it will be helpful to everyone. I would also like to thank everyone for their support of the 123WORDPRESS.COM website! You may also be interested in:
|
<<: Example code for implementing page floating box based on JS
In HTML, you need to specify the encoding used by...
The <TH> tag is used to set the properties ...
1. Command Introduction The ifconfig (configure a...
Before hiding: After hiding: CSS: Copy code The co...
On the server, in order to quickly log in to the ...
Preface The latest version of MySQL 8.0 is 8.0.4 ...
The traditional method is to write a square in a ...
There are probably as many modular solutions for ...
Table of contents 1. What is a transaction? 2. Th...
background When working on the blockchain log mod...
Table of contents Primary key constraint Unique C...
This article describes how to set the automatic c...
Recently I changed Apache to nginx. When I moved ...
Official Website https://cli.vuejs.org/en/guide/ ...
This article example shares the specific code of ...