Network performance effects of HTTP/1.1, CSS1, and PNG
SIGCOMM '97 Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication
SPNP: Stochastic Petri Net Package
PNPM '89 The Proceedings of the Third International Workshop on Petri Nets and Performance Models
Size-based scheduling to improve web performance
ACM Transactions on Computer Systems (TOCS)
Analysis and control of correlated web server queues
Computer Communications
Silo: exploiting JavaScript and DOM storage for faster page loads
WebApps'10 Proceedings of the 2010 USENIX conference on Web application development
| Hi-index | 0.00 |
In the development of HTTP protocol, the technique to overlap multiple HTTP requests and replies on single TCP connection, called 'keep-alive' or 'persistent connection', has won great success. It is already verified that, persistent connection could help to save the cost of frequently creating TCP connection, and could also reduce the number of operations such like forking and destroying process. Many years passed, persistent connection mechanism has been implemented widely to support all kinds of web services. However recently, dramatic changes to networking conditions and server computing capacity challenge the motivations of such mechanism and reveal some of its drawbacks. This paper models the connection management procedure in concurrent web servers with Petri Nets, and determines the parameters for the model by measuring a bunch of key metrics in modern web servers and networks. Plus, experiments are carried out in real modern test-bed with real traffic. The analytical results yielded by the model, along with experimental results, help us to clarify the negative role that persistent connection actually plays in modern web servers, especially in those busy ones.