Webmaster in the search for virtual host, often easy to "unlimited number of IIS connections, unlimited traffic" and other temptations, but a server to put hundreds of sites how can not be limited? Another idea, assuming that he does not limit the resources of each site, virtual host resources (CPU, memory, bandwidth, etc.) is always limited, so long as the hundreds of sites have a site to occupy more resources, other sites will be implicated. There is no freedom without restriction, and no limit is impossible.
The current virtual host is mainly divided into three types of restrictions:
One, the flow limit:
is to restrict network traffic directly, this restriction is usually the most severe one limit, 10 g of traffic roughly support 50 people online. The month after the flow of more than one months, the site can not be normal access, the solution is to upgrade space or increase traffic.
Second, CPU limit:
CPU restrictions do not appear to limit the IIS or network traffic, but because each program running requires a certain amount of CPU quotas, but also disguised traffic restrictions, often web page tip online is due to too little CPU limit. After refreshing or 15 seconds, you can get a temporary normal operation, and about 1% of the CPU limit is equivalent to 20 IIS connections. This is important for forum space, the Forum CPU limit once too small will not run normally.
Third, IIS restrictions:
IIS restrictions are now the most used, but also by the majority of users or host to accept, is a relatively loose flow limit scheme. Typically 20 IIS is equivalent to 1%CPU occupancy.
In short, the virtual host is not actually unrestricted, the overall divided into the above three ways, how you choose, depends on your needs. If your program uses little CPU, is optimized program, you can choose to limit the CPU, so that your online can get the greatest play; if you are a beginner, or a forum user, or a website program has a BBS, select IIS restrictions or direct traffic restrictions is a good choice.