|
|
|
[back to Domino 6 performance features]
The Domino 6 Web server supports HTTP 1.1 persistent connections
With HTTP 1.1 persistent connections, once a client and server open a connection, it remains open until the client or server specifically requests the connection be closed. While the connection is open, the client can send multiple (but separate) requests, and the server can respond to them in the order in which they are received. Clients are also free to send multiple requests without waiting for the responses, in effect "pipelining" the requests. For example, a client may do this when requesting all graphic images from a particular page. It can also make the requests sequentially, then listen for responses from the server. Persistent connections are on by default in Domino 6.
Persistent connections are especially useful in the following scenario:
- Browser opens a connection and retrieves a page containing multiple images.
- Browser opens a second connection and retrieves images over both connections.
- Browser closes the second connection and maintains the first connection. The server/browser closes this connection after a time-out or when the browser goes to another site.
For clients, persistent connections can make a noticeable difference on slow networks (for example, 56 Kb modems) when rendering a page. On fast networks (especially 100 MB/second), persistent connections aren't as beneficial because the cost of establishing a connection is very low compared to polling persistent connections.
Performance analysis of the Domino 6 iWA server (done on a 100 MB/second network) shows the number of users supported and resources used are about the same with or without persistent connections.
|
|
|
|
|
|