前言：
我在单个Amazon EC2实例前面有一个AWS Elastic Load Balancer。
我有3个其他EC2实例通过curl向负载均衡器发送请求。
对EC2 ip的直接请求具有稳定的响应时间和可接受的速度。
对ELB的请求平均响应时间更长，但速度并不理想。
我的观察结果几乎与此相同： https : //forums.aws.amazon.com/thread.jspa?messageID=419138
"ELB's backend requests to the EC2 instance expect to be on HTTP 1.1 keep-alive connections. The instance/server needs to either support keep-alive connections OR explicitly return response headers to ELB that note the connection is closed. Not returning that header and also not keeping alive the connection on the server results in ELB thinking the connection has been kept alive, waiting for ~30 seconds, and then retrying at that point with a new connection (hence the quick response times on the server, but slow perceived latency outside the ELB)." 我的问题：
从ELB转储响应头还有保持活动头。
直接从EC2实例转储响应头，它具有Connection: close 。
在通过ELB实例时，我仍然遇到了上述线程中提到的高度可变的速度/延迟，但据我所知，我已经明确地从EC2实例发回"Connection: close"头到ELB。
任何有识之士都非常感谢。