Enable journaling only if needed:
tune2fs -O has_journal /dev/sdX
Don’t ever disable journaling if you value your data.
Disk Scheduler Optimization
Change the I/O scheduler for SSDs:
echo noop > /sys/block/sda/queue/scheduler
For HDDs:
echo cfq > /sys/block/sda/queue/scheduler
Neither of these schedulers exist anymore unless you’re running a really ancient Kernel. The “modern” equivalents are none and bfq. Also this doesn’t even touch on the many tunables that bfq brings.
Also changing them like they suggest isn’t permanent. You’re supposed to set them via udev rules or some init script.
SSD Optimization
Enable TRIM:
fstrim -v /
Optimize mount settings:
mount -o discard,defaults /dev/sdX /mnt
None of this changes any settings like they imply.
Optimized PostgreSQL shared_buffers and work_mem.
Switched to SSDs, improving query times by 60%.
No shit. Who would’ve thought that throwing more/better hardware at stuff will make things faster.
EDIT: More bullshit that I noticed:
Use ulimit to prevent resource exhaustion:
ulimit -n 100000
Again this doesn’t permanently change the maximum number of open files. This only raises the limit for the user who runs that command. What you’re actually supposed to do is edit /etc/security/limits.conf and then relog the affected user(s) (or reboot) to apply the new limits.
Use compressed swap with zswap or zram:
modprobe zram echo 1 > /sys/block/zram0/reset
This reads like it was written by some LLM.
Don’t ever disable journaling if you value your data.
Neither of these schedulers exist anymore unless you’re running a really ancient Kernel. The “modern” equivalents are
none
andbfq
. Also this doesn’t even touch on the many tunables thatbfq
brings.Also changing them like they suggest isn’t permanent. You’re supposed to set them via udev rules or some init script.
None of this changes any settings like they imply.
No shit. Who would’ve thought that throwing more/better hardware at stuff will make things faster.
EDIT: More bullshit that I noticed:
Again this doesn’t permanently change the maximum number of open files. This only raises the limit for the user who runs that command. What you’re actually supposed to do is edit
/etc/security/limits.conf
and then relog the affected user(s) (or reboot) to apply the new limits.This doesn’t even make any sense.