3.4.1.2 Deriving Performance Parameters  

Having defined base performance parameters, lets look at how these parameters can be used 

to determine the performance of an HTTP transaction. The base performance parameters that 

are listed above can be used to derive more useful performance parameters as follows: 

Derived Parameter  

Description 

Derived By 

EntityUploadRate 

The rate of upload to the 

requestContentLength/ 

server of the request 

requestBodyEndTime  

message body  

requestBodyStartTime 

HeaderResponseTime 

The time elapsed from 

replyTime  requestTime 

sending a request and the 

request message body to a 

server, any processing by 

the server and the receipt of 

the reply header by the 

client. 

EntityDownloadRate 

The rate of download from 

replyContentLength/ 

the server of the request 

replyBodyEndTime  

message body 

replyBodyStartTime 

Table 2: Table of Sample Derived Performance Parameters 

Of course, there are numerous other parameters that could be derived. However, the derived 

parameters listed above give an example of what's possible. 

3.4.1.3 Interpretation of Derived Performance Parameters 

Further analysis of derived parameters above will now be undertaken to indicate their 

usefulness and situations there they are applicable. 

entityUploadRate:

 This gives a good indication as to the connectivity between the client 

and server and the ability of the server to process information sent to it. Typically this could 

only be used when the request has a message body such as when a POST or PUT method is 

used with an HTTP request.