|
|
This table outlines the relative load imposed on the server based on different types of load imposition. What is being described is based on eValid observations of the relative size (and hence download speed) of typical real-world website top pages, e.g. www.msn.com or www.cnn.com, etc.
This table identifies the quantitative differences between four logically consistent levels of detail to impose load on a website server:
These estimates are based only on download requirements and assume that there are no other limits. This is assuming in effect that there is an infinite capacity channel between the client browser machine and the machine that serves the pages.
The 100:1 ratio between full-page loading and rendering and between simple GETs is an estimate because in many instances, using eValid's internal timers, the time it takes just to get a typical basepage is less than 10 msec. eValid's internal timer has a 1 msec resolution, so the 100:1 ratio is thought to be conservative.
|
Estimated Equivalent Number of Simulated Users
Varying Conditions of Download Completeness and Varying Duty Cycles | ||||||
| Type of User Request (Affects Total Download Volume) | Relative Size of Download Request
(Total Page Download Size Including Images) | Simulated Users 1 Browser 5% Duty Cycle | Simulated Users 1 Browser 100% Duty Cycle | Simulated Users 100 Browsers 5% Duty Cycle | Simulated Users 100 Browsers 10% Duty Cycle | Simulated Users 100 Browsers 100% Duty Cycle |
| FULL Option Full Page Download/Rendering (Including Images) | 100 | 1 | 20 | 100 | 200 | 2,000 |
| TEXT Option Full Page Download/Rendering (No Images) | 33-1/3 | 3 | 60 | 300 | 600 | 6,000 |
| URL Option Specified URL BasePage Downloading Only (No LINKed files and No Images) | 1 | 100 | 2,000 | 10,000 | 20,000 | 200,000 |
| URL Option with 10 Shadows (No LINKed files and No Images) | 10 | 1,000 | 20,000 | 100,000 | 200,000 | 2,000,000 |
