Skip to main content

Limiting Bitrate and Network Throttling

We may limit incoming or outcoming data rates to/from our infrastructure to maintain the stability of our service for customers. Bitrate limitation is an action to limit the number of bits that can be passed through a transmission channel in a period of time. Network throttling is an intentional action to slow down transmission speed in a network channel. It is not only about limiting bitrate but also limiting the allowed number of requests in a period of time. There are several tools and techniques that can be used to apply bitrate limitation and network throttling.


Wondershaper

It is an easy-to-use tool for Linux and is already in the package repository. It can limit the bit rate that can be achieved by network interfaces in the system. We can install it by running the following command.

apt install wondershaper

We can choose an interface to have a limitation either or both on download and upload.

wondershaper <interface-name> <download-rate-in-bps> <upload-rate-in-bps>

For example, the following code will limit eth0 to 40k bits/s of download rate and 20k bits/s of upload rate.

wondershaper eth0 40000 20000

To clear the setting, we can run the following command.

wondershaper clear eth0

Trickle

Based on its manual page, Trickle is a tool to limit the download or upload rate of any applications that utilize the socket interface. We can read more information about this tool here. We need to remember that only programs with dynamic linking can work with Trickle. We can test whether a binary can work with Trickle by the following command.

ldd $(which [binary]) | grep libc.so
For example,
ldd $(which wget) | grep libc.so

If it shows the location of libc.so, it means the binary can work with Trickle. For instance, if we want to limit the download rate of the wget tool, we can use the following example.

trickle -d [rate in KB/s] wget [protocol://file-URL] 

Nginx

Nginx is actually a proxy server that provides plenty of features to help us serve our web-based services such as the request rate and bandwidth limiting capability. This feature is used to prevent DDoS attacks by preventing our server to handle too many requests. It needs a defined key to differentiate a client from another, a memory zone to keep states of all the keys, and a rate-setting that states the number of requests per second or minute. The examples are as follows.

http {
    #...
    limit_req_zone $binary_remote_addr zone=one:10m rate=1r/s;

    server {
        #...
        location /search/ {
            limit_req zone=one;
        }
        location /search2/ {
        	# if request rate > specified rate, 5 requests are queued
            limit_req zone=one burst=5; 
        }
        location /search3/ {
        	# 5 excessive requests are served immediately
            limit_req zone=one burst=5 nodelay; 
        }
        location /search4/ {
        	# 3 excessive requests are served immediately, 2 requests are delayed
            limit_req zone=one burst=5 delay=3; 
        }
    }
}

Bandwidth limiting is applied per connection while Nginx originally allows multiple connections. It means if we want the exact bitrate value to be provided for specific addresses, we can set Nginx to allow only one connection.

http {
    limit_conn_zone $binary_remote_address zone=addr:10m;
    
    # mapping for dynamic configuration
    map $ssl_protocol $response_rate {
      "TLSv1.1" 10k;
      "TLSv1.2" 100k;
      "TLSv1.3" 1000k;
    }

    server {
        root /www/data;
        limit_conn addr 5;

        location /download/ {
            limit_conn       addr 1;
            # rate limiting is applied after 1MB data is passed
            limit_rate_after 1m; 
            limit_rate       50k;
        }
        
        # dynamic configuration
        location /secure/ {
            limit_rate       $response_rate;
        }
    }
}

We can get more information from Nginx documentation.


Comments

Popular posts from this blog

Increase of Malicious Activities and Implementation of reCaptcha

In recent time, I've seen the increase of malicious activities such as login attempts or phishing emails to some accounts I manage. Let me list some of them and the actions taken. SSH Access Attempts This happened on a server that host a Gitlab server. Because of this case, I started to limit the incoming traffic to the server using internal and cloud firewall provided by the cloud provider. I limit the exposed ports, connected network interfaces, and allowed protocols. Phishing Attempts This typically happened through email and messaging platform such as Whatsapp and Facebook Page messaging. The malicious actors tried to share a suspicious link lured as invoice, support ticket, or something else. Malicious links shared Spammy Bot The actors leverage one of public endpoint on my website to send emails. Actually, the emails won't be forwarded anywhere except to my own email so this just full my inbox. This bot is quite active, but I'm still not sure what...

Configuring Swap Memory on Ubuntu Using Ansible

If we maintain a Linux machine with a low memory capacity while we are required to run an application with high memory consumption, enabling swap memory is an option. Ansible can be utilized as a helper tool to automate the creation of swap memory. A swap file can be allocated in the available storage of the machine. The swap file then can be assigned as a swap memory. Firstly, we should prepare the inventory file. The following snippet is an example, you must provide your own configuration. [server] 192.168.1.2 [server:vars] ansible_user=root ansible_ssh_private_key_file=~/.ssh/id_rsa Secondly, we need to prepare the task file that contains not only the tasks but also some variables and connection information. For instance, we set /swapfile  as the name of our swap file. We also set the swap memory size to 2GB and the swappiness level to 60. - hosts: server become: true vars: swap_vars: size: 2G swappiness: 60 For simplicity, we only check the...

Deliver SaaS According Twelve-Factor App

If you haven't heard of  the twelve-factor app , it gives us a recommendation or a methodology for developing SaaS or web apps structured into twelve items. The recommendation has some connections with microservice architecture and cloud-native environments which become more popular today. We can learn the details on its website . In this post, we will do a quick review of the twelve points. One Codebase Multiple Deployment We should maintain only one codebase for our application even though the application may be deployed into multiple environments like development, staging, and production. Having multiple codebases will lead to any kinds of complicated issues. Explicitly State Dependencies All the dependencies for running our application should be stated in the project itself. Many programming languages have a kind of file that maintains a list of the dependencies like package.json in Node.js. We should also be aware of the dependencies related to the pla...

Kenshin VS The Assassin

It is an assassin versus assassin.

Handling PDF Generation in Web Service

If we are building a website that requires a PDF generation feature, there are several options for implementing it based on the use cases or user requirements. First, we can generate the PDF on the client side using any available client library. It is suitable if the use case is to print out some data that is already available inside certain website components, and we want to maintain the styles of the components in the document. Second, we can do it fully in the back-end using any library available, such as PDF-lib, jsPDF, and so on. This approach is suitable if we want to keep the data processing or any related business functions in the back-end server. This second approach might have disadvantages, such as the difficulty of maintaining the design assets and styles which are already on our website. Third, it is using a hybrid approach, where certain processes are handled on the client side, and some are handled on the back-end. In this post, I want to discuss more about the...

Free Cloud Services from UpCloud

Although I typically deploy my development environment or experimental services on UpCloud , I do not always stay updated on its announcements. Recently, I discovered that UpCloud has introduced a new plan called the Essentials plan, which enables certain cloud services to be deployed at no cost. The complimentary services are generally associated with network components or serve as the foundation for other cloud services. This feature is particularly useful when retaining foundational services, such as a load balancer, is necessary, while tearing down all services and reconfiguring the DNS and other application settings each time we temporarily clean up infrastructure to reduce costs is undesirable.  When reviewing the service specifications of the cloud services in the Essentials plan, they appear to be very similar to those in the Development plan. The difference in service levels is unclear, but it could be related to hardware or resource allocation. For instance, the loa...