IX Web Hosting : Established in 1999, Hosting Hundreds of thousands of sites in our own data center.
Support Center
Managing Traffic
1. How do I change the traffic limit?
Traffic limits are set per plan and can't be changed. We unfortunately are not able to offer any custom changes or accommodations to our plans. If your account reaches its limit in a given month your account is subject to suspension. We do however offer throttle policies to help you regulate the amount of traffic you receive.
To enable the Throttle module, do the following:
- On the control panel page, click web options.
- Click the edit icon for the domain you wish to edit.
- Scroll the page to find the throttle policy option and turn it on.
- Select the type of policy and click submit.
- Complete the wizard.
- At the top of the web service page, click the apply link.
The eight throttling policies are:
- Concurrent:
Impose a limit on the number of concurrent requests at any one time. The period specifies how long data is accumulated before the counters are reset.
- Document:
Excluding requests for HTML page elements such as images and style sheets impose a limit on the number of requests per period. When this limit is exceeded, all further requests are refused, until the elapsed time exceeds the period length, at which point the elapsed time and the counters are reset. Note that the requests (hits) column of the throttle status display does not include the requests for page elements.
- Idle:
Impose a minimum idle time between requests. When the minimum is not reached, the request incurs a calculated delay penalty or is refused. First, whenever the elapsed time exceeds the period length, then the counters are reset. Second, if the idle time between requests exceeds the minimum, then the request proceeds without delay. Otherwise the request is delayed between one and the set maximum number of seconds. If the delay would exceed maximum, then the request is refused entirely to avoid occupying servers unnecessarily. The delay is computed as the policy minimum less the idle time between requests.
- Original:
Impose a limit on the volume (Kbytes sent) per period, which when exceeded the request incurs a counter-based delay penalty or is refused. First, whenever the elapsed time exceeds the period length, then the volume and elapsed time are halved.
Second, if the volume is below the limit, then the delay counter is decreased by one second if it is not yet zero.
Otherwise, when the limit is exceeded, the delay counter is increased by one second. The delay can be between zero and the set maximum number of seconds, after which the request will be refused to avoid occupying servers unnecessarily.
- Random:
Randomly accept a percentage (limit) of the requests. If the percentage is zero (0), then every request is refused; if the percentage is 100, then all requests are accepted. The period specifies how long data is accumulated before the counters are reset.
-
Request:
Impose a limit on the number of requests per period. When this limit is exceeded all further requests are refused until the elapsed time exceeds the period length, at which point the elapsed time and counters are reset.
-
Speed:
Impose a limit on the volume (Kbytes sent) per period, which when exceeded the request incurs a calculated delay penalty or is refused. First, whenever the elapsed time exceeds the period length, then the limit (allowance) is deducted from the volume, which can't be a negative result; also the period length is deducted from the elapse time. Second, if the volume is below the limit, in which case the request proceeds without delay. Otherwise the request is delayed between one and the set maximum number of seconds. If the delay would exceed the maximum, you refuse the request entirely to avoid occupying servers unnecessarily.
The delay is computed as one plus the integer result of the volume times 10 divided by the limit.
-
Volume:
Impose a limit on the volume (kbytes sent) per period. When this limit is exceeded all further requests are refused, until the end of the period at which point the elapsed time and counters are reset.
You can also set throttle policy to none which imposes no restrictions on a request and used as a place holder to allow monitoring. The limit currently serves no purpose. The period specifies how long data is accumulated before the counters are reset. Remember to apply the changes you have made. Press Apply in the Web Service -> Server Configuration row.
