Why does web hosting limit traffic and IIS connections

Formal mainstream space providers will carry out IIS and traffic display, such as Wanwang, China Netchao, etc. This is determined by the nature of web hosting, if you don't limit the resources of one server to be used by one web host, then other web hosts will not be able to run at all. Choosing to limit nothing is deceptive.

Virtual hosting is actually a region divided from the server, the resources of each server are limited, so the general space provider will limit the traffic and the number of IIS connections of each virtual host, so that if a virtual host exceeds the traffic or the number of connections is too much, only one site can be closed, and will not affect the others, and if the traffic and IIS are not restricted, as long as one of the sites is too traffic, it will cause all the sites on this server to be affected. The site is big and it's okay, the site is small and waiting to suffer, so it's not bad to limit the number of traffic and IIS connections, and you can choose a web host that suits your traffic and IIS when you buy.

Consider the host in the United States, and you don't have to be convicted. Limit and no limit are for different hosts, if the ** traffic is large, the web host even if it says unlimited traffic and unlimited number of links, it is also fake. For large traffic, you must choose a dedicated server.

Restrictions are good, but not restrictions are bad.

If you have to choose between the two. Of course, it's better to limit IIS. In fact, regular web hosting will definitely limit IIS.

Web hosting is carved out on a server. We know. There is a limit to the number of IIS connections to a server.

If you want all the virtual hosts on the server to be working properly. There is definitely also a need to limit the number of IIS connections per web host. The so-called unlimited means that you use more and others use less.

When others use more, you use less. Even when someone else occupies the IIS, your ** can't be opened. This is an irresponsible approach.

As for the traffic. Now basically all web hosting. VPS or servers are unmetered.

Don't know what you're seeing with the data-throttling web host.

Limit the flow of good and stable. Hosts that don't throttle traffic are often affected by a large number of users, which can be unstable, sometimes fast and sometimes slow.

As long as you don't have a lot of traffic, it's better to limit the traffic, and it's okay to limit it at the same time.

Some IDC providers claim that the number of IIS connections is not limited to the number of virtual hosts, which is purely to fool users: Analysis:

A server to run dozens or even hundreds of virtual hosts, if the IIS is not restricted, then the site with high traffic will eat a large number of IIS session threads, resulting in IIS overload, in win2000 there will be "too many users", win2003 directly prompt the service is unavailable. Of course, there are also operators who will manually adjust the amount of available memory of IIS processes and threads, and also adjust the cache size, the size of the paging and unpaged memory buffer pool, and the size of the paging file, so as to provide better performance, so that the IIS service will not be so easy to go down, but it is not a good thing not to limit IIS, for the virtual machine users with large access to take advantage of the opportunity to get more server hardware resources, but for the users with small visits, it is a big loss, and the resources are occupied, which is slowed down. Therefore, in order to increase transparency, Netshield Technology's virtual hosting has IIS restrictions, and the price of IIS connections is clearly marked.

Ensure the fair rights and interests of every user.

The number of IIS connections is how many people you allow to connect to you at the same time. The number of IIS connections is 100, and 100 people are allowed to connect to your ** at the same time, and 101 people open it is "the page cannot be displayed".

If you have access to 10G per month, then there is no limit to the number of people you can connect to. There can be n people connected, but if you have a web page with a size of 1k, and 1000 people open your web page at the same time, it is 1m traffic, 1000 times such operation traffic is 1g, and 10000 times 1000 people open this web page at the same time is 10g traffic. If you run out of 10G on the first day of the month.

Then for the rest of the day, your ** won't be able to open. The traffic limit means that the god can't open it when the traffic runs out, but it does not limit the number of people who connect.

Note: Sometimes IIS and traffic are limited at the same time!

I have a relationship with a service provider!

Most of the web hosts are limited to IIS, CPU!Limit the CPU%3 or 10 series, giving you this CPU, how much traffic can you run? Some hosts have a CPU limit %2, if a forum or program is not good, who is enough?!

If there are 50-100 IISs, how many interviews can I receive in a day? Some also limit traffic now, 5G, 10G, in fact, limit CPU, traffic, all suitable for small sites. If there are thousands or tens of thousands of visits per day, it won't be crowded into the host, and the traffic will not always exceed the CPU every day, and it will prompt dozens of hundreds of serv ......... every day

Generally, web hosting has a traffic limit, but there is no bandwidth limit.

Because there is not much traffic on the virtual host, if there is a lot of traffic, other things will be overloaded, such as CPU, memory, database, etc.

The number of visits is throttled, IIS throttling occurs requests, the number of connections exceeds the denial of service, and the traffic runs out and cannot be accessed.

There is no advantage, if you want performance, you can use VPS

General web hosting is limited, but not all of the ** on a server are always full load, and the impact is not large, if you are unlucky and a server with a large number of visits, it will be more or less affected.

But the average small ** is basically nothing, almost the enterprise** does not have so many visits.

Data throttling is not easy.

Find me to buy unmetered, high IIS connection web hosting.

It's just a joke to say that you don't limit the traffic, how can the web host not be restricted, you have to put dozens or even hundreds of stations on a server, if your station has too much traffic and affects others, do you think he may let you continue? There is no difference between the restriction of web hosting traffic and the non-limit, even if there is a limit, beyond the case of not affecting others, most of the space providers do not interfere with you

In a word, as long as it's something that is shared, and you influence others, you have to start thinking about the server side again.

Web hosting that does not limit traffic and IIS is generally unstable, and it is not recommended to buy, just like the web hosting I bought in Xiluo, the traffic and IIS are limited, but they are sufficient, and the server is stable.

Because web hosting is carved out on the server. What it shares is server bandwidth. Let's say the bandwidth of this server is 100M

In other words, all the virtual hosts on this server share 100M bandwidth. Therefore, there must be a maximum limit for each web host separately. In order to ensure the normal use of each user.

However, the bandwidth in Hong Kong is usually relatively small. It's also understandable that a single web host has a limit of 100kb. If your ** system has a large number of visits.

It is recommended that you use VPSThere will be at least 1M or more bandwidth.

Personal opinion. Hope it helps. If you have any questions, you can contact me.

That's 1M bandwidth.

This is just the uplink and downlink network bandwidth.

IIS limit is the user connection limit, to put it bluntly, it is the number of IIS connections, the higher this value, the better independent** It depends on how much PU you have.

You limit how many IPs you have per day.

It won't be so little, it's usually shared 100m.

It is recommended that you try it first, we have a trial, in order to facilitate the customer experience, we have Wanwang M3 space here for you to try for free.

The number of IIS concurrent connections refers to the first request to the server, and then the CSS, JS, **, etc. in this web page, each request is counted as an IIS concurrent number, so IIS is theoretically divided into several program situations.

There are several situations: (take 50 people in 100m space as an example) The user single-clicks ** your files, and disconnects them normally after the end, these connections are calculated according to instants, that is, your 50 people** can accept 50 points at the same time**; The user opens your page, even if it stays on the page and does not make any requests to the server, then within 15 minutes after the user opens one side, it must be counted as one**, that is, your 50 people**15 minutes can accept different users to open 50 pages In the case of b above, the user continues to open the same **other pages, then**The number of people is calculated according to the 15 minutes after the last click (request) of the user, In this 15 minutes, no matter how much the user clicks (including the opening of a new window), it is still one person**. When you have an iframe in your page, you need to double the number of frames for each additional frame!

Because this is equivalent to the user requesting multiple pages to the server at the same time. When the user opens the page and then closes the browser normally, the number of users will be cleared immediately. Then understand what the number of people in the forum is.

Forum** simply counts the number of active users over a certain period of time. The time here can be set by the user himself (delete the time of inactive users), and the default of the dynamic network forum is a relatively accurate value of 40 minutes. According to the above explanation, it is obvious that the concept of the number of connections in the forum ** and IIS is different For example, your **20IIS, there is an error message that there are too many IIS connections, and at this time your forum only shows 10 people** (assuming the **time is set to 20 minutes), then the correct explanation should be:

There are 20 connections to visit your, of which 10 are normal access to the forum.

1. Traffic limit.

It is to directly limit network traffic, which is usually the most severe kind of traffic limit, and the traffic of 10 G roughly supports 50 people**. After the monthly traffic is exceeded, it cannot be accessed normally within a month**, and the solution is to upgrade the space or increase the traffic!

2. CPU limit.

CPU limit seems to have no limit IIS or network traffic, but because each program runs requires a certain CPU quota, it is also a disguised traffic limit, usually too much web page display ** is caused by the CPU limit is too small! Temporary normal operation can be obtained after a refresh or 15 seconds, and usually 1% of the CPU limit is equivalent to 20 IIS connections! This is important for the forum space, and once the CPU limit of the forum is too small, it will not function properly!

Three: IIS limitations.

IIS limit is the most used now, and it is also recognized by most users or hosts, and it is the only loose traffic limit, usually 20 IIS is equivalent to 1% CPU occupation!