
| Time | Hits in Hour | KBs in Hour | Hits in Day | KBs in Day | Load Average |
| 11-12 PM | 431 | 1850 | 14498 | 61550 | 0.9 |
| 10-11 PM | 403 | 2250 | 14531 | 61880 | 0.3 |
| 09-10 PM | 591 | 2630 | 14344 | 60850 | 0.2 |
| 08-09 PM | 553 | 2220 | 14255 | 60140 | 0.3 |
| 07-08 PM | 723 | 2950 | 14060 | 59140 | 0.3 |
| 06-07 PM | 742 | 2850 | 13934 | 58870 | 0.3 |
| 05-06 PM | 846 | 3560 | 13712 | 58010 | 0.5 |
| 04-05 PM | 813 | 3660 | 13593 | 58250 | 0.3 |
| 03-04 PM | 907 | 3960 | 13368 | 57490 | 0.6 |
| 02-03 PM | 837 | 3730 | 13497 | 58100 | 1.5 |
| 01-02 PM | 957 | 4070 | 13524 | 57810 | 0.4 |
| 12-01 PM | 900 | 3810 | 13792 | 58450 | 0.4 |
| 11-12 AM | 984 | 4040 | 14052 | 59510 | 0.5 |
| 10-11 AM | 703 | 2900 | 14195 | 60380 | 0.5 |
| 09-10 AM | 868 | 3730 | 14142 | 60130 | 0.4 |
| 08-09 AM | 576 | 2350 | 14351 | 60770 | 0.4 |
| 07-08 AM | 616 | 2480 | 14281 | 60690 | 0.4 |
| 06-07 AM | 526 | 2070 | 14410 | 61060 | 0.3 |
| 05-06 AM | 302 | 1330 | 14339 | 60960 | 0.6 |
| 04-05 AM | 343 | 1430 | 14424 | 61290 | 0.2 |
| 03-04 AM | 291 | 1200 | 14454 | 61350 | 0.4 |
| 02-03 AM | 318 | 1220 | 14370 | 60950 | 0.2 |
| 01-02 AM | 276 | 1210 | 14407 | 60960 | 0.2 |
| 00-01 AM | 231 | 1090 | 14355 | 60840 | 0.2 |
| Average | 606 | 2577 | 14135 | 60039 | 0.4 |
The Load Factor shows how congested or backed up processes are on the server. The lower the Load Factor is the more resources are available to the user and the faster throughput on the server. The higher the Load Factor is the less resources are available and the slower the throughput on the server. I have the Load Factor on this page because I want to see if there is a correlation between low hit rates and transfers when there is a high Load Factor on the server. The Load Factor on this server has been known to range from a low of 0 to a high in excess of 40. The following scale provides you with some measure of how to interpret the Load Factors shown on the above chart.
All of the above performance descriptions are for the server only. There may be network delays that can significantly impact your perception of response. Because of Network overload or other network routing problems, your request for service to this server might be routed from Palo Alto to Chicago and then to Paris, back down to Los Angeles, out to St. Louis, and finally to this server located in Mountain View. You can evaluate and gauge some of these factors by looking at your status line in Netscape. While your packets are taking a grand tour of the US heartland and Europe, your status line will be saying Contacting Host. Eventually the message will state Host Contacted which means now you are waiting for packets to be sent back to your client machine. Again, the Packets may take a grand tour around half the world. You may think the host is slow while you are waiting for these world traveling packets to reach your desk. However the Load Factor might indicate that your request was handled instantly and all of the delay was due to a network overload and not a loaded server. You may also examine the route and the time taken by your packets from your site to our site by running our tracer route program. This program shows how much of the response time is due to congestion on the network.
We Welcome your suggestions, site recommendations, and comments - Contact Us