There are times when the hit rate at some particular location of your site is maximized, and your server may not be equipped to handle the increased congestion. It may lead to server crash, and hence site downtime. A bandwidth throttling device is a good solution as it blocks the user requests when the server reaches the bandwidth limit. It moves the users in a queue and their requested are processed, as soon as the bandwidth requirements gets a little below than acceptable level.In case of shared hosting, let’s say that you have a written agreement with your host that the other sites will not have any issues if your site begins to use too many resources at a time. Note that the host might have signed same contracts with other site owners whose sites are hosted at the same server. In a situation where you see a sudden increase in volume of transactions of your site, you will see that your site is disabled so that it does not affect other sites.
When you enable bandwidth throttling, Internet Information Services (IIS) activates a set of counters to monitor it in System Monitor – SysMon. These counters can be identified by "Async I/O" in the counter name. These counters are active only when bandwidth throttling is enabled.
If the bandwidth used approaches the maximum limit set by the user, bandwidth throttling blocks read requests, but allows write requests and transmission requests. Read requests are blocked first, because they are likely to result in further requests. Bandwidth throttling usually enables you to continue the user interaction session, for example – if you are submitting a
feedback request.
Even the best service providers can only serve as much bandwidth as one is capable of. Even in case of a dedicated server, if the site load exceeds specified limits, the site can be in trouble. So, the need to have a bandwidth throttling device increases tremendously when hundreds of sites are hosted on a single server as in case of shared hosting.
No comments:
Post a Comment