如何在春季启动中实现高一致性



我需要创建一个每秒支持 40 个并发用户的产品(我是并发工作的新手)

为了实现这一目标,我尝试开发一个hello world弹簧启动项目。 即,

弹簧启动 (1.5.9)

码头 9.4.15

具有获取端点的 rest 控制器

代码如下:

@GetMapping
public String index() {
return "Greetings from Spring Boot!";
}

在机器上运行的应用程序 Gen10 DL360

然后我尝试使用apachebench进行基准测试

75 个并发用户:

ab -t 120 -n 1000000 -c 75 http://10.93.243.87:9000/home/
Server Software:
Server Hostname:        10.93.243.87
Server Port:            9000
Document Path:          /home/
Document Length:        27 bytes
Concurrency Level:      75
Time taken for tests:   37.184 seconds
Complete requests:      1000000
Failed requests:        0
Write errors:           0
Total transferred:      143000000 bytes
HTML transferred:       27000000 bytes
Requests per second:    26893.28 [#/sec] (mean)
Time per request:       2.789 [ms] (mean)
Time per request:       0.037 [ms] (mean, across all concurrent requests)
Transfer rate:          3755.61 [Kbytes/sec] received
Connection Times (ms)
min  mean[+/-sd] median   max
Connect:        0    1  23.5      0    3006
Processing:     0    2   7.8      1     404
Waiting:        0    2   7.8      1     404
Total:          0    3  24.9      2    3007

100 个并发用户:

ab -t 120 -n 1000000 -c 100 http://10.93.243.87:9000/home/
Server Software:
Server Hostname:        10.93.243.87
Server Port:            9000
Document Path:          /home/
Document Length:        27 bytes
Concurrency Level:      100
Time taken for tests:   36.708 seconds
Complete requests:      1000000
Failed requests:        0
Write errors:           0
Total transferred:      143000000 bytes
HTML transferred:       27000000 bytes
Requests per second:    27241.77 [#/sec] (mean)
Time per request:       3.671 [ms] (mean)
Time per request:       0.037 [ms] (mean, across all concurrent requests)
Transfer rate:          3804.27 [Kbytes/sec] received
Connection Times (ms)
min  mean[+/-sd] median   max
Connect:        0    2  35.7      1    3007
Processing:     0    2   9.4      1     405
Waiting:        0    2   9.4      1     405
Total:          0    4  37.0      2    3009

500 个并发用户:

ab -t 120 -n 1000000 -c 500 http://10.93.243.87:9000/home/
Server Software:
Server Hostname:        10.93.243.87
Server Port:            9000
Document Path:          /home/
Document Length:        27 bytes
Concurrency Level:      500
Time taken for tests:   36.222 seconds
Complete requests:      1000000
Failed requests:        0
Write errors:           0
Total transferred:      143000000 bytes
HTML transferred:       27000000 bytes
Requests per second:    27607.83 [#/sec] (mean)
Time per request:       18.111 [ms] (mean)
Time per request:       0.036 [ms] (mean, across all concurrent requests)
Transfer rate:          3855.39 [Kbytes/sec] received
Connection Times (ms)
min  mean[+/-sd] median   max
Connect:        0   14 126.2      1    7015
Processing:     0    4  22.3      1     811
Waiting:        0    3  22.3      1     810
Total:          0   18 129.2      2    7018

1000 个并发用户:

ab -t 120 -n 1000000 -c 1000 http://10.93.243.87:9000/home/
Server Software:
Server Hostname:        10.93.243.87
Server Port:            9000
Document Path:          /home/
Document Length:        27 bytes
Concurrency Level:      1000
Time taken for tests:   36.534 seconds
Complete requests:      1000000
Failed requests:        0
Write errors:           0
Total transferred:      143000000 bytes
HTML transferred:       27000000 bytes
Requests per second:    27372.09 [#/sec] (mean)
Time per request:       36.534 [ms] (mean)
Time per request:       0.037 [ms] (mean, across all concurrent requests)
Transfer rate:          3822.47 [Kbytes/sec] received
Connection Times (ms)
min  mean[+/-sd] median   max
Connect:        0   30 190.8      1    7015
Processing:     0    6  31.4      2    1613
Waiting:        0    5  31.4      1    1613
Total:          0   36 195.5      2    7018

从上面的测试运行中,我自己在 27 个用户中实现了每秒 ~75K,但它看起来增加了用户也增加了延迟。此外,我们可以清楚地注意到连接时间正在增加。

我要求我的应用程序支持 40k 并发用户(假设所有用户都使用自己的单独浏览器),并且请求应在 250 毫秒内完成。

请帮我这个

我自己也不是这个话题的大巫师,但这里有一些建议:

有一个
  • 硬性限制,有多少请求可以处理一个实例,所以如果你想支持很多用户,你需要更多的实例
  • 如果您使用多个实例,则必须以某种方式在实例之间分配请求。一个流行的解决方案是Netflix Eureka。
  • 如果您不想维护额外的资源,并且产品将在云中运行,请使用提供的负载均衡服务(例如 AWS 上的负载均衡器)
  • 您还可以微调服务器的连接池设置

相关内容

  • 没有找到相关文章

最新更新