| 1 |
On 12/07/2020 11:59, Michael wrote: |
| 2 |
> On Sunday, 12 July 2020 09:29:08 BST Nikos Chantziaras wrote: |
| 3 |
>> No. But what you can do is lower its nice level to 19, and CPU and IO |
| 4 |
>> priority to "idle". |
| 5 |
>> |
| 6 |
>> schedtool -D -n 19 pid |
| 7 |
>> ionice -c 3 -p pid |
| 8 |
> |
| 9 |
> Another trick to use if the atom is becoming I/O disk bound is: |
| 10 |
> |
| 11 |
> echo bfq > /sys/block/sda/queue/scheduler |
| 12 |
> |
| 13 |
> This will have more of an impact if the PC is swapping heavily and the I/O on |
| 14 |
> /dev/sda is choking other processes accessing the disk. |
| 15 |
|
| 16 |
bfq seems to help a bit (although not as much as some years ago, when |
| 17 |
bfq was an actual disk scheduler rather than just a scheduling policy |
| 18 |
tweak.) |
| 19 |
|
| 20 |
I have bfq enabled by default for everything by putting the following in |
| 21 |
/etc/udev/rules.d/20-block.rules: |
| 22 |
|
| 23 |
ACTION=="add|change", SUBSYSTEM=="block", ATTR{queue/scheduler}="bfq" |
| 24 |
|
| 25 |
This will use bfq for all storage (including storage devices plugged in |
| 26 |
at runtime, like USB disks.) |
Archives