If you then continue to try to make requests faster than 15 rpm from multiple connections after your bucket is empty, you will eventually start seeing HTTP 503 errors being returned. If your bucket of requests ever gets empty, any further requests will be "slowed down" to 15 rpm. When your rpm is less than 15, the requests are returned to the bucket. In other words, when your rpm is greater than 15, requests are slowly "borrowed" from your bucket of 30,000 requests. Access to the Account Dashboard is unrestricted.įor Subversion and Webdav HTTP(S) connections, all accounts will be limited to 15 requests-per-minute (rpm), but allowed to "burst" up to 30,000 requests.
The following limits only apply to Trac, repository, and shared drive requests. Our goal is not to restrict our customers in any way besides discouraging short polling intervals on automated software. Out of fairness to our other customers, who experience slower performance as a result, we have had to implement the following QoS policy.
However, sometimes a customer will inadvertently set a very short polling interval, and this will result in tens of thousands of requests to our servers. These programs are very useful, and we support their use with Repository Hosting.
Netdrive trial reset software#
Many of our customers use continuous integration software or other software that automatically connects to their repositories on a regular basis to look for changes.
0 kommentar(er)
