Stuttering and/or freezing when loading programs or writing to boot SSD

[isaac0clarke (Isaac Clarke)]

@glb

To see which I/O scheduler your drives are currently using, run the following command:

$ for i in /sys/block/sd?/queue/scheduler; do echo "$i: $(<$i)"; done

~$ for i in /sys/block/sd?/queue/scheduler; do echo "$i: $(<$i)"; done
/sys/block/sda/queue/scheduler: none mq-deadline kyber [bfq] 
/sys/block/sdb/queue/scheduler: none mq-deadline kyber [bfq] 
/sys/block/sdc/queue/scheduler: none mq-deadline kyber [bfq] 
/sys/block/sdd/queue/scheduler: none mq-deadline kyber [bfq] 
/sys/block/sde/queue/scheduler: none mq-deadline kyber [bfq] 

I read that this is “for high performance SSDs and Nvme-s”.

.

@glb

To change one of the drives to the BFQ scheduler, run the following commands:

$ sudo -i
# echo bfq > /sys/block/sda/queue/scheduler
# exit

Note that the change will not persist across system reboots. You’ll have to create a “udev” rule if you decide that you want the setting to be the default on system startup.

For example:

# cat << END > /etc/udev/rules.d/60-ioscheduler-rotational.rules
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/scheduler}="bfq"
END

HTH.

This instead, other than having a brief breakdown (feel free to link any wiki page when you believe they’d be best) is something which I’d like to have for each and all systems.
I’d rather have “a superfast Nvme lose 2 seconds when copying 20gb” than “a superfast Nvme freezing for 1 minute because it’s copying 5gb” (this PC does not have the install on an Nvme, I’m just making a very practical example).

More than that, it’d be beneficial for those whom have a OLD computer (I’ll never leave a chance to link this work everywhere it’s relevant, both to help and because other than an “obsession” [fascination?] of mine) who just want to slam an SSD in there and run le desktop to read le taxes.