围困测试在一段时间后停止击中api

Question

我正在使用siege加载测试我的api（nginx）.Api将POST请求从nginx转发到运行在8082的kafka rest服务器。

我正在使用四台ec2机器进行围攻。每当我看到围攻停止打了一段时间然后恢复。所以我强行用Ctrl + C打破围攻，我可以看到以下内容：

HTTP/1.1 200   0.01 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.01 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.01 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.01 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.01 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.01 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.01 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.02 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.03 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.03 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.02 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
^C
Lifting the server siege..      done.

Transactions:              10699 hits
Availability:             100.00 %
Elapsed time:              26.71 secs
Data transferred:           1.23 MB
Response time:              0.05 secs
Transaction rate:         400.56 trans/sec
Throughput:             0.05 MB/sec
Concurrency:               20.11
Successful transactions:       10699
Failed transactions:               0
Longest transaction:            1.67
Shortest transaction:           0.00

如果我不停止它，那么它会在一段时间后恢复击中，然后再次停止击打。当我强行阻止它时：

HTTP/1.1 200   0.06 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.07 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.04 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.03 secs:     121 bytes ==> POST http://my-ip/topics/jsontest
HTTP/1.1 200   0.04 secs:     121 bytes ==> POST http://my-ip/topics/jsontest


^C
Lifting the server siege..      done.

Transactions:              21399 hits
Availability:             100.00 %
Elapsed time:             133.88 secs
Data transferred:           2.47 MB
Response time:              2.97 secs
Transaction rate:         159.84 trans/sec
Throughput:             0.02 MB/sec
Concurrency:              474.16
Successful transactions:       21399
Failed transactions:               0
Longest transaction:           63.23
Shortest transaction:           0.00

现在又一次能够达到21399-10699 = 10700大致相同的命中率。所以我想理解为什么它会在10699次点击后停止打击一段时间？ ec2-machine的限制？它只是降低了我的交易率，因为10699次点击后需要等待一段时间。我不想要的。这种情况发生在所有四台机器上。现在我的api在ec2实例上。但我可以从四台机器中分别打到10699次。但交易率非常低。

任何帮助表示赞赏!!