Optimization guide for Linux

*************Optimize your Linux system step by step*********************
*************************************************************************


#############################################################
Easily choose kernel, recovery mode and get into BIOS update:
##############################################################

    sudo nano /etc/default/grub
Lines must be like these ones:
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=3
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

sudo update-grub

**************************************
OPTIMIZE LAPTOP BATTERY LIFE:
**************************************


First, install tlp:
    sudo apt install tlp -y

After installing TLP on your Linux machine, make sure it is enabled on startup and start the service:
Make an autostart with these commands:
    sudo systemctl enable tlp.service && sudo systemctl enable tlp.service

To view the current TLP configurion, system information, active power saving settings and battery data, run:
    sudo tlp-stat

***Disable USB auto suspend***

When TLP is started with default configuration, some USB devices will be automatically suspended to save power when your Laptop is running on battery. To disable USB autosuspend, edit /etc/tlp.conf file:
    sudo nano /etc/tlp.conf

Find the following line and set its value as 0.
    USB_AUTOSUSPEND=0

You can also exclude specific devices from USB autosuspend (separate with spaces). First, use lsusb command to get the ids. Then, mention the device ids with space-separated like below
    USB_BLACKLIST="8078:0014 065d:8023"


If you're using Thinkpad, you will install any one of the following packages. If you don't know exactly which package to install, run tlp-stat -b command as sudo or root user. It will guide you which package to install.

    acpi-call-dkms - External kernel module providing battery recalibration for newer ThinkPads (X220/T420 and later).
    tp-smapi-dkms - External kernel module providing battery charge thresholds, recalibration and specific tlp-stat -b output for older ThinkPads.

After installing TLP on your Linux machine, make sure it is enabled on startup and start the service using commands:
    sudo systemctl enable tlp.service
    sudo systemctl start tlp.service


 ***Increase battery life by disabling the Bluetooth driver***

If you rarely use Bluetooth, you can probably increase the battery life of your laptop a lot by disabling the Bluetooth driver (instead of simply disabling the Bluetooth feature). Like this:
    echo "blacklist btusb" | sudo tee /etc/modprobe.d/blacklist-bluetooth.conf
Reboot your computer.

***How to undo (re-enabling Bluetooth support):***
a/ Temporary re-enabling Bluetooth can be done with this terminal command:
    sudo modprobe -v btusb
This will instantly re-enable Bluetooth, but it won't survive a reboot.

b/ Permanent re-enabling of Bluetooth can be achieved by the following terminal command which removes the Bluetooth module from the blacklist:
    sudo rm -v /etc/modprobe.d/blacklist-bluetooth.conf
Then reboot your computer. Bluetooth should be available again permanently.

GUI client for tlp (provides applet indicator and more functions:
sudo add-apt-repository ppa:slimbook/slimbook
sudo apt update
sudo apt install slimbookbattery

If you want to have an applet to choose the governance mode (powersave or performance):
sudo apt install indicator-cpufreq




****************************
TRICKS TO PRESERVE YOUR SSD:
****************************

***Reduce swappiness (set swappiness to 5)***
    sudo bash -c 'echo "vm.swappiness=5" >> /etc/sysctl.conf'
Reboot or type:
    sudo sysctl -p
Check:
    sysctl vm.swappiness

On a computer with less than 8GB ram, you should use zram:
    sudo apt install zram-config
Check if it works: cat /proc/swaps

***Mount /tmp as /tmpfs***

 The Linux temporary file directory (/tmp) is very busy with applications and the system continually writing small files to it, sometimes quickly created and deleted. This directory is emptied at each reboot, but it remains on disk, which causes a lot of writing.

It is possible to put it in RAM with tmpfs.
Add these lines at the bottom of /etc/fstab:
    tmpfs /tmp tmpfs defaults,relatime,mode=1777,nosuid,size=4196M 0 0
    tmpfs /var/tmp tmpfs defaults,relatime,mode=1777,nosuid,size=4196M 0 0
Reboot.

 Here we have created a /tmp of 4 GB, which is more than enough. Don't hesitate to put such a large value, even on a machine with little RAM: tmpfs only consumes memory when storing data.
You can put other directories in tmpfs in the same way, but remember that as soon as the machine reboots or shuts down, you will lose the files placed in these directories.

***

 The ext4 file system has a parameter called commit. This is the maximum time that passes between the moment an application requests to write data to disk and the moment ext4 will actually write it to disk. By default, this value is set to 5 seconds. ext4 will therefore wait at most 5 seconds before writing data to disk.
  ext4 has a relative intelligence: For example if a file is created and then deleted in these 5 seconds, it will not write anything to disk (it is useless, since the file is deleted). By setting the commit time to 60 seconds, you can avoid disk writes.

Note that setting the commit to 60 seconds means that if your computer crashes, you risk losing the last 60 seconds of disk writes (instead of the default 5 seconds). It's up to you to see if your disk operations are critical at this point.

In the mount options of your partitions (/etc/fstab), simply add the option commit=60:
    UUID=4a5773ef-7833-4741-c53f-8de2dd3d7527 /               ext4    errors=remount-ro,commit=60 0       1


 ***Set the automatic TRIM job to daily***
6. The cleaning action TRIM is recommended for the good performance of your SSD in the long run. Otherwise it might become slow after some time.

That's even true for new SSD's: although new SSD's nowadays usually have some form of garbage collection integrated into their firmware, it's always better to execute a regular TRIM as well.

Note: very old SSD's from before 2010 usually don't support TRIM.

In Linux Mint and Ubuntu automatic TRIM is enabled by default, when you install them on an SSD. Namely by a weekly "job". But in many (most?) cases, once a week isn't frequent enough: waiting an entire week before recoverable disk space becomes usable again, is simply too long.

You can switch your system to automatic daily trimming as follows:

a. Copy/paste the following command line into the terminal, in order to create a new folder:
    sudo mkdir -v /etc/systemd/system/fstrim.timer.d
then:
    sudo nano /etc/systemd/system/fstrim.timer.d/override.conf
Copy/paste this:

[Timer]
OnCalendar=
OnCalendar=daily

Note: the double entry for OnCalendar is no mistake but intentional!

Save the modified file and reboot your computer.

Confirm that you've successfully edited trim's configuration by executing this terminal command:
    systemctl cat fstrim.timer

Your output should look approximately like this:
    # /lib/systemd/system/fstrim.timer
    [Unit]
    Description=Discard unused blocks once a week
    Documentation=man:fstrim
    ConditionVirtualization=!container

    [Timer]
    OnCalendar=weekly
    AccuracySec=1h
    Persistent=true

    [Install]
    WantedBy=timers.target

    # /etc/systemd/system/fstrim.timer.d/override.conf
    [Timer]
    OnCalendar=
    OnCalendar=daily

Let's take a look at this output. The first part shows the default setting (weekly), the second part shows the overriding setting that you've applied. That overriding setting contains two elements: first the existing OnCalendar setting (weekly) is being deleted, and then a new OnCalendar setting is being applied (daily).

If you ever want to check whether fstrim has actually happened, and when it happened, you can use this terminal command:
    journalctl | grep fstrim.service

***Gain 30% Linux Disk Performance***
By setting "noatime,nodiratime", you disable the "access time stamp", that the operating system puts on a file whenever it's being read by the operating system. For an SSD "noatime,nodiratime" might be better, because it reduces the disk writes somewhat.
Simply add “noatime,nodiratime” to your filesystem mount options in /etc/fstab to prevent atime from being updated on file and directory accesses:
         sudo nano /etc/fstab
         /dev/mapper/vgmint-root /               ext4    errors=remount-ro,commit=60,noatime,nodiratime 0       1
Reboot.

 ***Disable Java in Libre Office***
The performance of Libre Office might be enhanced greatly, when you disable Java in it. This will disable a few features, but usually you won't even miss those.
    Toolbar Libre Office Writer - Tools - Options...
    LibreOffice - Advanced - Java Options:
remove the tick for: Use a Java runtime environment


***VirtualBox***
In order to guarantee the integrity of virtual disks, when a guest OS (in a VM) performs a disk write, VirtualBox forces the disk write in the host system (by doing a sync).
One can reduce this forced write and have VirtualBox use the host system's disk cache. Not only does this greatly improve performance, but it also allows ext4 to possibly group disk writes.
In the settings of your virtual machine, go to Storage and on each controller (IDE, SATA...) check the box "Use host I/O cache".



***************************************
Limit the disk write actions of Firefox
***************************************

You can limit the disk write actions of Firefox, by putting the Firefox network cache into the RAM and by disabling sessionstore. Like this:

***Putting the Firefox network cache into the RAM***
By moving the Firefox network cache from your hard disk to the RAM, you diminish the amount of disk writes. This'll probably make your Firefox noticeably faster as well. The price you pay is small: it'll only "cost" you 1 GB of your RAM.

Note: don't do this when your computer has only 2 GB of RAM or less! Because with very little RAM, even 512 MB can't be missed.

Proceed like this:

a. Type in the URL bar of Firefox:
    about:config
Press Enter.

b. Now you're being presented with a warning. Ignore it and click on the button "I accept the risk!".

c. Copy/paste the following into the filter bar (search bar):
    browser.cache.disk.enable

Toggle its value to false by double-clicking it: this will disable "cache to disk" entirely.

d. Now you're going to make sure that "cache to RAM" is enabled (it is by default, but it may have been changed earlier). Copy/paste the following into the filter bar (search bar):
    browser.cache.memory.enable

This should already be set to true; if not, toggle it to true by double-clicking it.

e. Then you're going to determine how much memory can be used as RAM cache. Copy/paste this into the filter bar (search bar):
    browser.cache.memory.capacity
That entry should exist already (if not, create it now).

The current integer value will probably be -1, which automates the maximum size of the RAM cache dependent on the available amount of RAM. So far so good, but this automation usually creates a cache that's far too small....

So set it to 524288 (KB, which equals a maximum of 512 MB). That's usually enough for all amounts of RAM. But if you have RAM to spare, I recommend 1048576, which equals a maximum of 1 GB.

f. Close Firefox and launch it again. You're done! Check it like this:

Type in the URL bar:
    about:cache
Press Enter.

By the way: you'll then also see a mention of an "appcache" which might still be present on the disk, but there's absolutely no need to move that (much less frequently used) cache to the RAM as well.

Note: This is a user preference. Repeat this hack in each user account.

***Limit sessionstore***
9.2. Firefox has a session restore feature, which remembers what pages were opened if Firefox experiences an unexpected shutdown (read: crashes). This feature is neat, but causes many disk writes. Too many for an SSD. Limit it like this:

a. Type in the URL bar of Firefox:

    about:config

Press Enter.

b. Now you're being presented with a warning. Ignore it and click on the button "I accept the risk!".

c. Type the following keyword into the filter bar: sessionstore

d. Double-click on the item called browser.sessionstore.interval. The default interval is 15000, which means 15 seconds. Make it becomes 2 minutes: 120000 and click the OK button.

e. Close Firefox and launch it again.

Note (1): Leave the other cache and sessionstore settings as they are: usually, the less invasive a hack is, the better. Because this reduces the risk of unexpected unwanted side effects.

Note (2): This is a user preference. Repeat this hack in each user account.

***Optimize the Places database***
In your Firefox profile there's an sqlite database called Places, which after a while starts resembling a swollen Swiss cheese with holes. That might slow your Firefox down.

You can speed your Firefox up a bit, by optimizing (vacuuming) that database: you can namely deflate that swollen Swiss cheese into a compact smaller cheese. As follows:

Type the following in the URL bar of Firefox:
    about:support
Press Enter.
Almost at the bottom of the page you get to see then, there's a header called Places Database. Click there on the button called Verify Integrity.
You're done! Repeat this on a monthly basis, so that your Firefox won't lose speed again because of a swollen database.


*******************
Optimize the cache
*******************

    about:config
    browser.cache.use_new_backend
Click on the "+" symbol
Value "True" should be showed. That's all!

This optimised cache is by default not activated because it can cause tabs to crash in certain cases. This depends on the configuration and is random. If this happens, simply redo the procedure and deactivate this cache.

****************************
List of must-install addons:
****************************
Modules complémentaires (about:support)
-----------------------

Nom: Anti-Adblock Blocker
Type: extension
Version: 0.0.7
Activé: true
ID: {7616a0b7-d0b6-4a0d-ad65-c9b35d96bad4}

Nom: Bing
Type: extension
Version: 1.3
Activé: true
ID: bing@search.mozilla.org

Nom: Buster: Captcha Solver for Humans
Type: extension
Version: 1.3.2
Activé: true
ID: {e58d3966-3d76-4cd9-8552-1582fbc800c1}

Nom: Bypass Paywalls Clean
Type: extension
Version: 2.8.6.0
Activé: true
ID: {d133e097-46d9-4ecc-9903-fa6a722a6e0e}

Nom: ClearURLs
Type: extension
Version: 1.25.0
Activé: true
ID: {74145f27-f039-47ce-a470-a662b129930a}

Nom: Dark Reader
Type: extension
Version: 4.9.59
Activé: true
ID: addon@darkreader.org

Nom: Default Zoom
Type: extension
Version: 1.1.3
Activé: true
ID: default-zoom@jamielinux.com

Nom: Disable WebRTC
Type: extension
Version: 1.0.23
Activé: true
ID: jid1-5Fs7iTLscUaZBgwr@jetpack

Nom: DuckDuckGo
Type: extension
Version: 1.1
Activé: true
ID: ddg@search.mozilla.org

Nom: eBay
Type: extension
Version: 1.3
Activé: true
ID: ebay@search.mozilla.org

Nom: Expire History By Days
Type: extension
Version: 1.3.1
Activé: true
ID: expire-history-by-days@bonardo.net

Nom: Get Image Info
Type: extension
Version: 1.5.0
Activé: true
ID: @getimageinfo

Nom: Google
Type: extension
Version: 1.2
Activé: true
ID: google@search.mozilla.org

Nom: HTTPS partout
Type: extension
Version: 2021.7.13
Activé: true
ID: https-everywhere@eff.org

Nom: I don't care about cookies
Type: extension
Version: 3.4.3
Activé: true
ID: jid1-KKzOGWgsW3Ao4Q@jetpack

Nom: LocalCDN
Type: extension
Version: 2.6.38
Activé: true
ID: {b86e4813-687a-43e6-ab65-0bde4ab75758}

Nom: Qwant
Type: extension
Version: 1.2
Activé: true
ID: qwant@search.mozilla.org

Nom: Return YouTube Dislike
Type: extension
Version: 3.0.0.6
Activé: true
ID: {762f9885-5a13-4abd-9c77-433dcd38b8fd}

Nom: Reverso - Traduction, dictionnaire
Type: extension
Version: 2.2.205
Activé: true
ID: context@reverso.net

Nom: Search by Image
Type: extension
Version: 5.3.0
Activé: true
ID: {2e5ff8c8-32fe-46d0-9fc8-6b8986621f3c}

Nom: SponsorBlock pour YouTube - Supprime les publicités intégrées
Type: extension
Version: 5.1.1
Activé: true
ID: sponsorBlocker@ajay.app

Nom: SteamDB
Type: extension
Version: 3.6.1
Activé: true
ID: firefox-extension@steamdb.info

Nom: Tampermonkey
Type: extension
Version: 4.18.0
Activé: true
ID: firefox@tampermonkey.net

Nom: To DeepL
Type: extension
Version: 0.7.0
Activé: true
ID: {db420ff1-427a-4cda-b5e7-7d395b9f16e1}

Nom: TrackMeNot
Type: extension
Version: 0.10.46
Activé: true
ID: trackmenot@mrl.nyu.edu

Nom: uBlock Origin
Type: extension
Version: 1.44.4
Activé: true
ID: uBlock0@raymondhill.net

Nom: Universal Bypass
Type: extension
Version: 13.15.2.1
Activé: true
ID: {529b261b-df0b-4e3b-bf42-07b462da0ee8}

Nom: Wayback Machine
Type: extension
Version: 3.1
Activé: true
ID: wayback_machine@mozilla.org

Nom: Wikipédia (fr)
Type: extension
Version: 1.1
Activé: true
ID: wikipedia@search.mozilla.org

Nom: Windscribe - Free Proxy and Ad Blocker
Type: extension
Version: 3.4.7
Activé: true
ID: @windscribeff

Nom: Youtube Audio
Type: extension
Version: 0.0.2.5
Activé: true
ID: {580efa7d-66f9-474d-857a-8e2afc6b1181}

Nom: English (CA) Language Pack
Type: locale
Version: 106.0.2buildid20221025.065831
Activé: true
ID: langpack-en-CA@firefox.mozilla.org

Nom: English (GB) Language Pack
Type: locale
Version: 106.0.2buildid20221025.065831
Activé: true
ID: langpack-en-GB@firefox.mozilla.org

Nom: Français Language Pack
Type: locale
Version: 106.0.2buildid20221025.065831
Activé: true
ID: langpack-fr@firefox.mozilla.org

*********************************************************
How to Enable DNS-over-HTTPS and Encrypted SNI in Firefox
*********************************************************
-What is DNS-over-HTTPS (DoH)? DoH encrypts DNS traffic with HTTPS (port 443) and HTTP/2 and requires authentication of the requested server.
-What is Encrypted SNI? The Server Name Indication (SNI) shares the hostname for outgoing TLS connections in plain-text. Encrypting SNI is another way to secure your web activity from man-in-the-middle (MITM) attacks. Encrypted SNI is enabled by default with the Cloudflare DNS resolver.

Enable DNS-over-HTTPS (DoH):
    Open your Firefox Preferences page
    Under Network Settings, select Settings
    Check Enable DNS over HTTPS
    Select OK

Enable encrypted SNI:
    In your browser, navigate to about:config;
    Type network.security.esni.enabled
    Select the toggle button to the right of false to true

*****************************************
Limiting the disk write actions of Chrome
*****************************************

10. The disk write actions of Google Chrome can be limited as follows.

a. Click on the three dots (vertical line) in the upper right of the Chrome window - Settings.

b. Section Privacy and security - Cookies and site data
Preload pages for faster browsing and searching: disable it.

c. Close Chrome and launch it again.

This way, you've disabled the "preload" feature, which can cause a lot of extra network traffic and also a lot of writes.


*****************************************************
 Speed up your wireless internet (some WiFi chipsets)
*****************************************************

The easiest way to speed up your wireless internet connection by disabling power management for the WiFi chipset.Type in the terminal:
    iwconfig
You can then not only see the name for your wireless chipset (for example: wlp2s0), but also whether Power Management is on for it. When it's off, or when no mention is made of Power Management at all, you don't need to do anything.
When Power Management is on, proceed as follows:
    sudo nano /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
Change 3 into 2.
Save and reboot.
Then check in the terminal, by the command iwconfig, whether Power Management for the wireless chipset is off now.  If so, you're done!

Is your WiFi not working properly? You may have forgotten to set the frequencies for the "France" region (as a result, channels 11/12/13 are not accessible).

    Check the value: iw reg get. If you don't see Country: FR then it's not set correctly.
 Change the REGDOMAIN parameter in the /etc/default/crda file. Set it to:  REGDOMAIN=FR
If the crda file doesn't exist, just create it in /etc/default


*************************************
 Speed up your Intel wireless chipset
*************************************

If you have a (reasonably) modern wireless chipset from Intel, it'll run on the iwlwifi driver. If so, you might be able to increase its speed noticeably, by turning on Tx AMPDU for it.
  The purpose of AMPDU is to improve data transmission by aggregating or grouping together several sets of data. Thus it sharply reduces the amount of transmission overhead.
  It used to be "on" by default in the iwlwifi driver. But several years ago, it was turned off because of stability issues on a few wifi chipsets. This problem affects, however, only a minority of chipsets...

For turning it on, proceed like this:
a. First check whether your chipset runs on the iwlwifi driver:
    lsmod | grep iwlwifi

Does the terminal output contain the word iwlwifi (in red letters)? If so, proceed with the next step:

b. Use copy/paste to transfer the following line (it's one line!) to the terminal. Don't type it; it's too easy to make typing errors:
    echo "options iwlwifi 11n_disable=8" | sudo tee /etc/modprobe.d/iwlwifi-speed.conf

Don't be confused by the name of the option: when it's set to 8, you don't actually disable anything but you enable something.
c. Reboot your computer.

as your wifi become unstable? Then undo the iwlwifi hack as described below.

Problems? Then undo it like this
Does the iwlwifi hack create stability issues for your wifi? Then undo it with the following terminal command:
 sudo rm -v /etc/modprobe.d/iwlwifi-speed.conf
Then reboot. All should be then, as it was before.

*****************************************
Enable performance support for Intel CPUs
*****************************************

Create a new config file:
    sudo nano /etc/sysctl.d/99-i915.conf
Copy-paste this line:
    dev.i915.perf_stream_paranoid=0
Save and reboot

**************************
 Turn off the firewall log
***************************

Have you enabled the firewall ufw (which is recommended)? Then you'll probably never look at its logs, so it won't hurt to turn off all logging by the firewall. Especially because it can be rather spammy sometimes. Turning off its log can save some system resources and disk space, and can be done like this:
    sudo ufw logging off
Do you want to enable logging by the firewall again?
    Do you want to enable logging by the firewall again?

**************************
Enable High Quality Audio
**************************

Edit /etc/pulse/daemon.conf, copy/paste these lines:
default-sample-format = float32le
default-sample-rate = 48000
alternate-sample-rate = 44100
default-sample-channels = 2
default-channel-map = front-left,front-right
default-fragments = 4
default-fragment-size-msec = 25
resample-method = soxr-vhq
remixing-produce-lfe = no
remixing-consume-lfe = no
high-priority = yes
nice-level = -11
realtime-scheduling = yes
realtime-priority = 9
rlimit-rtprio = 9
daemonize = no

Type this to make the modifications effective:
    pulseaudio --kill && pulseaudio --start

How to determine default-sample-format:
    lscpu | grep 'Byte Order'
output: Little Endian

In my case it’s Little Endian hence I have selected float32le. If your output returns Big Endian then select float32be sampling format.

resample-method:
The resampling algorithm to use. I have selected soxr-vhq. It is the point sampler, which offers better sound quality however it is CPU intensive.If you have an old slow CPU, you should better use speex-float-10:
; resample-method = speex-float-10
Keep in mind the difference in CPU power required to re-sample audio mattered in 2005. Perhaps it meant something in 2010. It's mostly irrelevant on modern desktop machines.

More informations about the other options: https://medium.com/@gamunu/enable-high-quality-audio-on-linux-6f16f3fe7e1f
    pulseaudio --kill && pulseaudio --start


########################################
Boost your system with a custom kernel:
########################################
https://xanmod.org or https://liquorix.net/ (try both)

Before rebooting, check performance with your current kernel:
    sudo apt install glmark2
    glmark2
Save the ouput, reboot on the custom kernel and do the benchmark again, compare and choose the best.

######################
Clear systemd journal
######################
    crontab -e
* * * * 5 sudo journalctl --vacuum-time=7d

###############################################
DNS block-list to filter ads/tracking/malwares
###############################################
    crontab -e
* * * * 7 sudo curl https://sebsauvage.net/hosts/raw > /etc/hosts && sed -i 1i"127.0.0.1 Elitebook850G8" /etc/hosts

##########################
Set custom DNS permanently
##########################
Edit /etc/dhcp/dhclient.conf by adding:
supersede domain-name-servers <adresse du serveur DNS1>, <adresse du serveur DNS2>;

#For instance:
supersede domain-name-servers 1.1.1.1, 9.9.9.9;


#################################
Optimize your graphic performance
#################################
Add the Kisak PPA:
    sudo add-apt-repository ppa:kisak/kisak-mesa

It's strongly recommended to remove this PPA before upgrading to a newer Ubuntu release or using another mesa PPA.
    sudo apt install ppa-purge
    sudo ppa-purge ppa:kisak/kisak-mesa

Note: Using ppa-purge with Ubuntu derivatives needs to include -d <based_on_name> to work safely. For example, Linux Mint 20 is based on Ubuntu Focal, so that would make it:
    sudo ppa-purge -d focal ppa:kisak/kisak-mesa

#############################################################
Install Microsoft fonts (Verdana, Arial, Times New Roman,...)
#############################################################

sudo apt install ubuntu-restricted-extras msttcorefonts

*****************************************************
Useful tool to install: System Monitoring Center
****************************************************
Option-1) Installing for current user account: pip install system-monitoring-center
Option-2) Installing for system-wide: sudo pip install system-monitoring-center (This method can be used for preventing source code modifications.)

*********************
Tame the inode cache
*********************

Computers with at least 12 GB of memory (RAM), will probably benefit by shrinking the inode cache less aggressively.
The price that you pay for this, is that certain system items will remain longer in the RAM memory, which decreases the amount of available RAM for general tasks. That's why this tweak is only useful for computers with at least 12 GB of memory (RAM).
This is how you do it:

Edit etc/sysctl.conf

Scroll to the bottom of that text file and add your cache parameter to override the default, so copy/paste the following lines into that text file:

# Improve cache management
vm.vfs_cache_pressure=50

Save and reboot your computer.