when client requests will peak or sent responses will be huge, sometimes exceeding the capacity of parts of network and causing congestion, especially in parts of the network that form bottlenecks. This can cause data request failures, or in worst cases, server crashes. In order to prevent such occurrences, a client / server / system administrator may enable (if available) bandwidth throttling: at , to control the speed of ingoing (received) data and/or to control the speed of outgoing (sent) data: a client program could be configured to throttle the sending (upload) of a big file to a server program in order to reserve some network bandwidth for other uses (i.e. for sending emails with attached data, browsing web sites, etc.); a server program (i.e. web server) could throttle its outgoing data to allow more concurrent active client connections without using too much network bandwidth (i.e. using only 90% of available bandwidth in order to keep a reserve for other activities, etc.); examples: assuming to have a server site with speed access to Internet of 100MB/s (around 1000Mbit/s), assuming that most clients have a 1MB/s (around 10Mbit/s) network speed access to Internet and assuming to be able to download huge files (i.e. 1 GB each): with bandwidth throttling, a server using a max. output speed of 100kB/s (around 1Mbit/s) for each TCP connection, could allow at least (or even 10000 if output is limited to 10kB/s) (active connections means that data content, such as a big file, is being downloaded from server to client); without bandwidth throttling, a server could efficiently serve only (100MB/s / 1MB/s) before saturating network bandwidth; a saturated network (i.e. with a bottleneck through an Internet Access Point) could slow down a lot the attempts to establish other new connections or even to force them to fail because of timeouts, etc.; besides this new active connections could not get easily or fastly their proper share of bandwidth. at , to control the speed of data received or sent both at low level (data packets) and/or at high level (i.e. by inspecting application protocol data): policies similar or even more sophisticated than those of application software level could be set in low level network devices near Internet access point. Application A bandwidth intensive device, such as a server, might limit (throttle) the speed at which it receives or sends data, in order to avoid overloading its processing