Stone Steps Inc.

Article ID: Q20050728-01

Q: Why my file download times are lower than they really are?

A:The time reported in the AvgTime column of the URL report shows average amount of time the web server spent serving HTTP requests for each of the distinct URLs analyzed by Stone Steps Webalizer and, in general, is different from the file download time. 

For example, if the browser downloaded a single file using more than one HTTP request, the log file will contain a log record for each of the submitted requests, as shown in the sample below. The first response was returned with the status code 200, which may have been interrupted after 5342 bytes were transferred. When the browser reconnected in a few minutes, it did not restart the transfer from the beginning, but instead continued from the point where it was interrupted and requested next 501791 bytes of the same file using the Range header field. The server returned the requested part of the file with the status code 206, indicating a partial transfer. Then the browser requested the remaining 524590 bytes of the file.

 Date       Time      URL                        Response   Size  ProcTime
2005-07-27 04:55:31 /downloads/webalizer_win.zip    200     5342     6359
2005-07-27 04:57:11 /downloads/webalizer_win.zip    206   501791   101187
2005-07-27 04:57:34 /downloads/webalizer_win.zip    206   524590   128156

The first HTTP response returned 5342 bytes and was processed in about 6 seconds; the second one returned the next 502 KB of the requested file and kept the server busy for about 101 second; the last response retuned the remaining part of the file, 524 KB, and took about 128 seconds. 

Consequently, the overall file download time for webalizer_win.zip will be 235.70 seconds, but the average URL processing time for this file will be 78.57 seconds, which will be reported in the AvgTime column of the URL report.