GoServe: Response time recording

Response time recording

GoServe records the response times of the most recent one hundred transactions.

'Response time', here, means the time from when the client connection is accepted to when the first data bytes are sent. It may include the time to receive some or all data from the client, but does not include the time taken waiting for data to become available at the server. It also does not include the time taken to send the response (which may be very large, and dependent of network delays). Response times of transactions ended due to a timeout or other limit being exceeded are not recorded.

The average response time, to the nearest 0.01 second, is shown on the main GoServe window, next to the transactions count (unless an error has occurred). A more precise figure, along with the number of transactions over which it was recorded, is included in the CONTROL STATISTICS response (this figure will not reflect the response time of the transaction that initiates the CONTROL STATISTICS command). The same, more precise, figure is also shown on the 'Response' page of the Options notebook.

The average read wait time (the time taken waiting for data to become available at the server) is also shown on the CONTROL STATISTICS result. The sum of this and the average response time gives the average total elapsed response time, as observed by the server.

The GoServe response time directly affects the response time seen by the person using the client browser, so it is desirable to keep this as low as possible; the 'Response goal' setting in the Options notebook is provided to make it easier to judge the performance of your server setup. The read wait times are not included in response times so that the graph and averages only reflect delays that are under the control of the server.

The response times record may be reset using CONTROL RESET RESPONSE (or the Actions menu item 'Reset response times').

[ previous section | GoServe | next section ]