{"id":1713,"date":"2023-09-08T08:16:59","date_gmt":"2023-09-08T08:16:59","guid":{"rendered":"https:\/\/www.dedicatedcore.com\/blog\/?p=1713"},"modified":"2025-01-15T09:26:55","modified_gmt":"2025-01-15T09:26:55","slug":"add-swap-space-ubuntu","status":"publish","type":"post","link":"https:\/\/www.dedicatedcore.com\/blog\/add-swap-space-ubuntu\/","title":{"rendered":"How to Add Swap Space on Ubuntu 16.04 | 18.04"},"content":{"rendered":"

On Ubuntu 16.04, swap space can be quite important for maximizing system speed. particularly on systems with low amounts of physical memory. When physical RAM runs out, the system can temporarily store dormant memory pages in swap space, which functions as virtual memory.<\/p>\n

This tutorial will walk you through the process of adding swap space to your Ubuntu 16.04 system. It runs more smoothly and doesn’t crash because of memory issues. For the support of data science and machine learning<\/a> for Python allocation, the anaconda is been used. As mentioned the purpose of anaconda installation is a task you need to understand in detail.<\/p>\n

Examine the System for Information on Swaps<\/h2>\n

We can see if the system has any swap space available before we start. While it is possible to have more than one swap file or swap partition, one should suffice.<\/p>\n

Entering this will show us if the system has any swap configured:<\/p>\n

$ sudo swapon --show<\/pre>\n
If no output is returned, swap space is not currently available on your machine.<\/p>\n
You can use the following free utility to confirm that there isn’t an ongoing swap:<\/p>\n
$ free -h<\/pre>\n
\"check<\/strong><\/p>\n
The output’s “Swap” row shows you that the system is not currently in use for any swaps.<\/p>\n
Examine the Hard Drive Partition’s Available Space.<\/h3>\n
Using a separate partition just to allocate space for swap is the most popular method. It isn’t always feasible to change the partitioning scheme, though. A swap file that is stored on an already-existing partition can be made just as simply.<\/p>\n
We should first type the following to see how much disk space is being used:<\/p>\n
$ df -h<\/pre>\n
\"check<\/strong><\/p>\n
In this instance, the device under \/dev is our disk. In this scenario, we have plenty of space (only 1.1G used). You’ll most likely use it differently.<\/p>\n
The right size for a swap space is a matter of opinion, but ultimately it comes down to your preferences and the specifications of your application. Generally speaking, a decent starting point is to add twice as much RAM as your system has. Anything more than 4G of swap is generally unnecessary if you only use it as a RAM fallback, which is another wise maxim.<\/p>\n
Make a Swap File.<\/h3>\n
We can create a swap file inside our filesystem now that we are aware of the amount of hard disk space that we have available. In our root (\/) directory, we will create a file called swapfile with the desired swap size. The fallocate software is the most effective method for producing a swap file. With this command, a file with a preallocated size is created quickly.<\/p>\n
As the server in our case has 512MB of RAM, we will use this approach to build a 1 Gigabyte file. Modify this to suit your own server’s requirements:<\/p>\n
$ sudo fallocate -l 1G \/swapfile<\/pre>\n
By typing: we can confirm that the appropriate quantity of space was reserved.<\/p>\n
$ ls -lh \/swapfile<\/pre>\n
We have allocated the appropriate amount of space when creating our file.<\/p>\n
Activating the Swap File<\/h3>\n
We need to convert this into swap space now that we have a file available in the appropriate size. Initially, we must restrict the file’s permissions such that only users with root access can view its contents. This has serious security consequences because it keeps regular users from accessing the file.<\/p>\n
To restrict file access to only root, type:<\/p>\n
$ sudo chmod 600 \/swapfile<\/pre>\n
Type this to confirm the permissions change:<\/p>\n
$ ls -lh \/swapfile<\/pre>\n
\"enabling<\/strong><\/p>\n
As you can see, read and write flags are only enabled for the root user.<\/p>\n
The file can now be designated as swap space by typing:<\/p>\n
$ sudo mkswap \/swapfile<\/pre>\n
\"mark<\/strong><\/p>\n
Once the file has been marked, we may activate the swap file so that our system can begin using it:<\/p>\n
$ sudo swapon \/swapfile<\/pre>\n
By typing:, we can confirm that the swap is available.<\/p>\n
$ sudo swapon --show<\/pre>\n
\"verify<\/strong><\/p>\n
To confirm our conclusions, we can review the output of the free utility once more:<\/p>\n
$ free -h<\/pre>\n
\"check<\/strong><\/p>\n
After successfully configuring our swap, our operating system will use it when needed.<\/p>\n
Set the swap file as a permanent one.<\/h4>\n
The swap file is now active for this session thanks to our recent modifications. But the server won’t automatically remember the swap settings if we reboot. By including the swap file in our \/etc\/fstab file, we can alter this.<\/p>\n
The \/etc\/fstab file should be backed up in case something goes wrong:<\/p>\n
$ sudo cp \/etc\/fstab \/etc\/fstab.bak<\/pre>\n
You can type the following to append the swap file information to the end of your \/etc\/fstab file:<\/p>\n
$ echo '\/swapfile none swap sw 0 0' | sudo tee -a \/etc\/fstab<\/pre>\n
Adjust the Swap Settings<\/h4>\n
When it comes to swapping, there are a few configuration choices that you may play with to see how your system performs.<\/p>\n
Modifying the Swappiness Characteristic<\/h4>\n
The frequency at which your system moves data from RAM to the swap area is set by the swappiness option. A number between 0 and 100 is used to represent the percentage. The kernel won’t swap data to the disk unless it is required with values around zero. Recall that swap file interactions are “expensive” in the sense that they can significantly impair performance and take a lot longer than RAM interactions. In general, your system will operate faster if you tell it not to rely as much on the swap.<\/p>\n
To maintain more RAM-free space, values that are closer to 100 will attempt to swap out more data. This might be preferable in some circumstances, depending on the memory profile of your apps or the purpose of your server.<\/p>\n
By typing, we may view the swappiness value as of right now.<\/p>\n
$ cat \/proc\/sys\/vm\/swappiness<\/pre>\n
\"can<\/strong><\/p>\n
A swappiness setting of 60 is not too bad for a desktop computer. You may want to shift the server closer to 0. Using the sysctl command, we can change the swappiness value.<\/p>\n
For example, we may type: to set the swappiness to 10.<\/p>\n
$ sudo sysctl vm.swappiness=10<\/pre>\n
\"for<\/strong><\/p>\n
This configuration won’t change till the following reboot. We may add the following line to our \/etc\/sysctl.conf file to set this value automatically at restart:<\/p>\n
$ sudo nano \/etc\/sysctl.conf<\/pre>\n
At the end, you can include:<\/p>\n
\"at<\/strong><\/p>\n
Close and save the file when you’re finished.<\/p>\n
Changing the Cache Pressure Configuration<\/h4>\n
It is possible that you would also like to adjust the vfs_cache_pressure value. The amount that the system will prioritize caching inode and dentry information over other data is configured by this parameter.<\/p>\n
In essence, this is filesystem access data. It is sometimes very expensive to search and highly requested, so it is a great idea for your system to cache this. You may query the proc filesystem once more to see the current value:<\/p>\n
$ cat \/proc\/sys\/vm\/vfs_cache_pressure<\/pre>\n
\"adjusting<\/strong><\/p>\n
Our system deletes inode information from the cache as soon as it is right now. By typing: we can adjust this to a more cautious setting, such as 50.<\/p>\n
$ sudo sysctl vm.vfs_cache_pressure=50<\/pre>\n
\"output<\/strong><\/p>\n
Once more, this is exclusive to our present meeting. In the same way that we added our swappiness parameter to our configuration file, we can modify that:<\/p>\n
$ sudo nano \/etc\/sysctl.conf<\/pre>\n
Add the line with your revised value at the bottom:<\/p>\n
\"add<\/strong><\/p>\n
Close and save the file when you’re finished.<\/p>\n
Wrapping Up about How to Add Swap Space on Ubuntu<\/h4>\n
Finally, swap space addition for Ubuntu 16.04 is a simple procedure that can greatly improve system stability and speed, especially on systems with low physical memory. You can efficiently boost your system’s memory capacity, enabling more seamless multitasking and averting memory-related problems, by following the instructions provided in this guide. For a real-time search and analysis<\/a> of log data, Elasticsearch has been used and to understand the installation of Elasticsearch on Ubuntu one needs to follow the steps particularly.<\/p>\n
If you follow this guide’s instructions, you’ll be able to avoid out-of-memory exceptions in certain situations. Swap space is a very helpful tool for preventing some of these typical issues. Optimizing your application configurations or upgrading your server is the best course of action if you are experiencing OOM (out-of-memory) errors or if your system is not able to run the apps you require.<\/p>\n
Frequently Asked Questions (FAQ)<\/h4>\n
1. What is Swap Space?<\/strong><\/p>\n
It is a virtual memory file used by the operating system. It is used to extend physical RAM. When physical RAM is full, the system stores less frequently used data in swap space to free up RAM for more active processes.<\/p>\n
2. Which method is better for Adding Swap Space?<\/strong><\/p>\n
There are two methods for adding swap space as follows:<\/p>\n
Swap Files: <\/strong>Swap files are more flexible and easily resized but they have less performance than swap partitions.<\/p>\n
Swap Partition: <\/strong>Swap partitions are more performant than swap files but they require proper planning and are not more flexible.<\/p>\n
So both have their advantages and disadvantages and you can choose which is better for your requirement.<\/p>\n","protected":false},"excerpt":{"rendered":"
On Ubuntu 16.04, swap space can be quite important for maximizing system speed. particularly on systems with low amounts of physical memory. When physical RAM…<\/p>\n","protected":false},"author":1,"featured_media":1830,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.dedicatedcore.com\/blog\/wp-json\/wp\/v2\/posts\/1713"}],"collection":[{"href":"https:\/\/www.dedicatedcore.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dedicatedcore.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dedicatedcore.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dedicatedcore.com\/blog\/wp-json\/wp\/v2\/comments?post=1713"}],"version-history":[{"count":10,"href":"https:\/\/www.dedicatedcore.com\/blog\/wp-json\/wp\/v2\/posts\/1713\/revisions"}],"predecessor-version":[{"id":2637,"href":"https:\/\/www.dedicatedcore.com\/blog\/wp-json\/wp\/v2\/posts\/1713\/revisions\/2637"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dedicatedcore.com\/blog\/wp-json\/wp\/v2\/media\/1830"}],"wp:attachment":[{"href":"https:\/\/www.dedicatedcore.com\/blog\/wp-json\/wp\/v2\/media?parent=1713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dedicatedcore.com\/blog\/wp-json\/wp\/v2\/categories?post=1713"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dedicatedcore.com\/blog\/wp-json\/wp\/v2\/tags?post=1713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}