构建高性能web之路------web服务器长连接.docxVIP

构建高性能web之路------web服务器长连接web服务器都提供长连接的方式，所谓长连接就是客户端一次请求完后，不关闭连接，保持一段时间的连接，下次此客户端再次请求时，不用创建新连接，复用所保持的连接即可。从理论上，长连接可以免去大量建立和关闭连接的资源消耗，但同时也有大量连接被占用的代价。因此可以初步判断长连接比短连接能带来更高的TPS，更低的CPU消耗，更少的IO，更高的内存占用，下面通过实战来验证。服务器环境和测试工具可以见工具和环境准备篇本次web服务器选用apache prefork模式，apache长短连接的选择可以配置httpd.conf里的KeepAlive选项，如：KeepAlive On：长连接KeepAlive Off：短连接另外如果选择长连接还需配置KeepAliveTimeout和MaxKeepAliveRequests，其中KeepAliveTimeout为每个长连接服务端保持时长，默认配置为15秒，MaxKeepAliveRequests为每个长连接服务请求最大数，默认配置为100次，本次试验保持默认配置。使用ab来压apache，如：短连接环境下： /usr/alibaba/install/httpd-2.0.63-prefork/bin/ab -c 100 -n 1000000 http://localhost/长连接环境下： /usr/alibaba/install/httpd-2.0.63-prefork/bin/ab -c 100 -n 1000000?-k?http://localhost/同时都已100个并发请求apache默认首页1000000次然后通过ab测试结果、nmon收集资源消耗和strace跟踪实际调用三个维度来考察短连接和长连接的区别。1）ab测试结果短连接：[python]?view plain?copyConcurrency?Level:??????100??Time?taken?for?tests:???190.754776?seconds??Complete?requests:??????1000000??Failed?requests:????????0??Write?errors:???????????0??Total?transferred:??????1891115351?bytes??HTML?transferred:???????1456088816?bytes??Requests?per?second:????5242.33?[#/sec]?(mean)??Time?per?request:???????19.075?[ms]?(mean)??Time?per?request:???????0.191?[ms]?(mean,?across?all?concurrent?requests)??Transfer?rate:??????????9681.50?[Kbytes/sec]?received??Connection?Times?(ms)????????????????min??mean[+/-sd]?median???max??Connect:????????0????8???3.7??????8??????44??Processing:?????1???10???3.8??????9??????79??Waiting:????????0????7???3.0??????7??????61??Total:??????????4???18???5.7?????17?????101??长连接：[python]?view plain?copyConcurrency?Level:??????100??Time?taken?for?tests:???59.509558?seconds??Complete?requests:??????1000000??Failed?requests:????????0??Write?errors:???????????0??Keep-Alive?requests:????990148??Total?transferred:??????1927566346?bytes??HTML?transferred:???????1456007280?bytes??Requests?per?second:????16804.02?[#/sec]?(mean)??Time?per?request:???????5.951?[ms]?(mean)??Time?per?request:???????0.060?[ms]?(mean,?across?all?concurrent?requests)??Transfer?rate:?????