CFS Zen Tweaks is a bash script and systemd service that tweak the Linux CPU scheduler for better desktop responsiveness when under heavy CPU utilization.
The default kernel settings are not tweaked for desktop usage, with high throughput being prioritized over latency, notes the CFS Zen Tweaks author. This results in a less responsive desktop under heavy CPU load. Using CFS Zen Tweaks, you should notice an improved desktop responsiveness – for example, its author mentions that before using this, YouTube would lag while compiling code, and that’s no longer the case using the CFS Zen tweaks.
The CFS Zen Tweaks project adjusts the default kernel CPU scheduler (CFS or Completely Fair Scheduler) for better desktop responsiveness. The CFS CPU scheduler settings come from Linux ZEN kernel, which was created to provide a better Linux kernel for everyday systems.
Note that only the CFS CPU scheduler tweaks are used from the ZEN kernel, while this custom kernel also has other tweaks.
The advantage of using these tweaks over installing a custom kernel is that you get to keep your Linux distribution’s official kernel packages (so you get official updates and there’s no risk of breaking stuff).
It’s important to note though, that using these tweaks will increase the battery drain on laptops, due to more context switches.
Download CFS Zen Tweaks
CFS Zen Tweaks is packaged as a DEB (for Debian, Ubuntu, Linux Mint, Pop!_OS, etc.), RPM (Fedora), and it’s also available on AUR for Arch Linux / Manjaro users. If you just want the script and systemd service, visit the project GitHub repository page. To use it, you’ll need bash, gawk, and systemd to apply the settings on boot (these will be installed as dependencies if you’re using the prebuilt packages).
After installing the package, enable the tweaks to be applied on boot (and apply them right now) by using:
https://codecubit.com/wp-content/uploads/2022/08/AVvXsEgv0cXLMjV_7YtByCHnzmpUnaW0TYFnpTd3B9BO14tuw2kM9USx3-010u5MyOYxqQDUlI6tJAOdpMA0_oOdk1zLrxDs5itOzZgZFQNHKy9uKMVbz5YRNMFypFEf_uF5JpDKHBPqmWGCBnzY2NkiY2yH0LG1OBGYsWAm3Y73YnSrZ5pKhGb-nLoP9Z6jw640-h360.webp360640RoboLinuxhttps://codecubit.com/wp-content/uploads/2022/05/logo340x156.svgRoboLinux2022-08-10 19:41:292022-08-10 19:54:01Get Better Desktop Responsiveness Under Heavy CPU Load Using CFS Zen Tweaks
“A load balancer receives requests and then transfers them to targets defined in a target group. We can create an Application Load balancer either using the AWS management console or AWS CLI. There are several routing options with AWS Application Load Balancer, e.g., Host-Based routing.
In Host-based routing, incoming traffic is routed on the basis of the domain name or host name given in the Host Header. In this tutorial, we are going to create an Application Load balancer with Host-Based routing.”
Overview of This Lab
In this lab, we will set up Application Load Balancer on AWS using the host-based routing approach. To perform this lab, we require the following components: First, we need two availability zones with a minimum of one EC2 instance in each of them. Next is a VPC with at least one public subnet in each of these availability zones. We will configure the load balancer using these public subnets. Finally, configure a web server for the above EC2 instances and use the security group to open the port 80 for http requests on these instances.
Configuring the EC2 Instances
The first EC2 instance is an Ubuntu 20.04 Linux machine, and the web server (apache) displays the message: “This is an xyz host”. It has a hostname: www.xyz.tecofers.com
Similarly, the second instance is also an Ubuntu 20.04 Linux, with the web server displaying the message: “This is an abc host”. It has a hostname: www.abc.tecofers.com
The web servers contain the “abc” and “xyz” directories inside their root directories, i.e. (/var/www/).
Setting up the Target Group
Step 1. In this step, we will create target groups(“xyz” and “abc”) for routing the incoming requests. On the EC2 dashboard, select the Target Groups option on the left pane under the Load Balancing title. Now select the “Create target group” option:
Step 2. The “Specify group details” page has several options to be filled.
i) We start with the “Basic configuration” heading:
For the “Choose a target type” option, click the “Instances” radiodifusión button here.
For the “Target group name”, enter an appropriate target group name(“xyz” in my case).
For the “Protocol” and “Port” options, select “HTTP” and “80”, respectively.
For the “VPC” option, choose the VPC containing your instances.
Finally, for the “Protocol version,” stick to the default option(HTTP1).
ii) The “Health checks” Configuration has the following fields:
For the “Health check protocol” drop-down menu, choose HTTP.
For the “Health check path”, specify a custom path or use the default one(recommended).
We recommend keeping the “Advanced health check settings” as it is. Adding tags is an optional step. Enter “Next” to continue.
Register the Instances
In this step, we need to register the instances with the Target Groups.
Step 1. On this page, choose an instance and then select the button “Include as pending below”. This will make the instance appear in the “Review targets” heading. Proceed by hitting the “Create target group” button.
For another target group, “abc”, repeat the same steps of creating a target group and then attach another instance here. On the Target groups, the two target groups will appear as:
So far, we have not attached any Load balancer to our target groups. Let’s go and create a load balancer.
Create the Application Load Balancer
Note: Creating a load balancer service requires you to pay AWS.
Step 1. On the EC2 dashboard, select the Load Balancers title and hit the “Create Load Balancer” button, and then choose “Application Load Balancer”:
Step 2. Enter a name for the load balancer that satisfies the naming constraints. Under the Scheme, keep the default option (“Internet-facing”) selected. For “IP address type,” choose IPv4.
Step 3. On moving ahead, we have “Network mapping”; here, choose the VPC we are working with. Also, choose two availability zones that hold the targets. The incoming traffic will be routed to these targets by the load balancer.
Step 4. For the Security Groups, select or create a new security group for the load balancer that will allow communication with the target port (port 80)
Step 5. Now come the Listeners and routing segment; what we have to do here is to configure a listener by choosing a protocol(HTTP here) and a port. For the Default action, choose your target corresponding to the “forward to” field.
Step 6. Adding tags and Add-on services are optional steps and can be skipped. After reviewing the configuration summary and click the “Create load balancer” button:
The load balancer is now ready.
Add the Host-based Forwarding Rules
After the load balancer is created and its status becomes active, we are required to add traffic forward rules.
Step 1. From the “Load Balancers” page and select the load balancer and then further move to the Listeners tab:
Step 2. Navigate to the Listeners tab and under the “Rules” column, click on the “View/Edit rules” link. A new page appears here first; click on the “+” icon, then click on the “Insert Rule” link.
Step 3. For the IF(all match) column, do as follows:
i) click on the “+ Add condition” and set “Host header” as the type of Rule.
ii) enter the host or domain name inside the field corresponding to the label “is”.
Step 4. For the “Then” column, do as follows:
I) click on “+Add action” and set “Forward to” as the action.
ii) choose the target group.
Save the rule and for another target group, insert the rule in the same way and save it.
In case the above rules are not satisfied, the default rule will be used.
Register the Domain
To make the host-based routing work over the internet, we have to register the hostnames with Route 53 and map them with the load balancer DNS.
Step 1. From the Route 53 dashboard, choose the “Create hosted zone” option:
Step 2. Next, enter your domain name to where traffic will be routed to. For the “type” field, set “Public hosted zone”. Hit the button “Create hosted zone”.
Step 3. In the “Records” section, choose “Create record”.
Step 4. On the “Choose routing policy’ page, select the link “Switch to wizard” and then choose the “Simple Routing” box and click “Next”:
Step 5. Now choose “Define simple record” and then enter the record details:
Domain: domain or subdomain name to route the traffic to.
Record type: DNS type of the record.
Value/Route traffic to:
Choose “Apelativo to Application and Classic Load Balancer”
Choose the region where the load balancer is deployed
Choose the load balancer address and hit “Define simple record”.
On the next page, click on the “Create records” button.
Do the same steps for another domain name and verify the above record on the “Configure Records” page.
Test the Setup
To verify the above procedure, on a web browser, enter the DNS name of the load balancer along with the hostnames:
We have finally made the way to host-based routing on the AWS application load balancer. Try to do this lab yourself and also try to configure the Application Load balancer with path-based routing.
Click on the different category headings to find out more. You can also change some of your preferences. Note that blocking some types of cookies may impact your experience on our websites and the services we are able to offer.
Essential Website Cookies
These cookies are strictly necessary to provide you with services available through our website and to use some of its features.
We provide you with a list of stored cookies on your computer in our domain so you can check what we stored. Due to security reasons we are not able to show or modify cookies from other domains. You can check these in your browser security settings.
Google Analytics Cookies
These cookies collect information that is used either in aggregate form to help us understand how our website is being used or how effective our marketing campaigns are, or to help us customize our website and application for you in order to enhance your experience.
If you do not want that we track your visit to our site you can disable tracking in your browser here:
Other external services
We also use different external services like Google Webfonts, Google Maps, and external Video providers. Since these providers may collect personal data like your IP address we allow you to block them here. Please be aware that this might heavily reduce the functionality and appearance of our site. Changes will take effect once you reload the page.
Google Webfont Settings:
Google Map Settings:
Google reCaptcha Settings:
Vimeo and Youtube video embeds:
The following cookies are also needed - You can choose if you want to allow them: