it's literally 2019 and doing any heavy i/o still locks up my desktop with a fucking ssd completely. why is this accepted?
It's literally 2019 and doing any heavy i/o still locks up my desktop with a fucking ssd completely...
Connor Green
Other urls found in this thread:
groups.google.com
twitter.com
Julian Hill
what filesystem? Never had this with XFS.
Lincoln Turner
As opposed to the I/O galore you enjoy on Windows? Check your scheduler, fagit.
Jayden Thompson
ext4 and mq-deadline
Alexander Scott
Unironically Works on my machine. This is actually why I switched /to/ Linux as it's much better than Windows superfetch bullshit
Kayden Lopez
What ext4 options? I hope you are at least using journal_async_commit.
Also, you want to set the scheduler to "none" for SSDs; you want to feed them data as soon as it is ready to go since you don't have to wait for a mechanical head to move across the disk.
Asher Jenkins
>Deadline
Just disable that shit completely. Even on ata, the drive will have it's own internal scheduler. I don't get why do scheduler is even used by default anymore. They disable it by default for nvme.
Brandon Hill
>falling for the SSD meme
Benjamin Clark
Caleb Murphy
this
Kayden Price
What is a Linux operating system, exactly? Just an OS that uses Linux, like Android or z/OS? Because those are pretty radically different and shouldn't really be grouped together like that.
Gabriel Rivera
As opposed to NTFS on windows? Don't make me laugh.
Leo Long
why the fuck is everything an us vs them to you? i just want to use my desktop without everything grinding to a halt every time i update my packages or some shit, last time i used windows was 10 years ago
thanks for the tips everyone
Ian Morris
Oh God I hate this problem. I think the writing buffer is actually too big. I have resolved by logging in as root
>su root
then setting the dirty bytes to a set number (I guess the default setting 0 actually doesn't give any cap to how much should the writing cache be large), by typing:
>echo $((16*2048*2048)) > /proc/sys/vm/dirty_background_bytes
>echo $((48*2048*2048)) > /proc/sys/vm/dirty_bytes
I chose that size as a good compromise but this shit took a lot of googling to figure out. I only ever found it when copying a large file from an external drive to my computer, not usually the other way round.
Angel Nelson
>As has been noted (not only by me), the linux kernel is a miniscule part of a complete system.
>Linus, groups.google.com
Ryan Brooks
Year of the Linux desktop
Anthony Walker
>the linux kernel
Thank you for the 69152011 post, the anonymous poster.
Hunter Thompson
>superfetch
>mfw
Carson Lewis
works on my machine
Nathan Anderson
You're welcome.
Isaac Wood
What's your package manager and filesystem? Could be related to that. I use apt with ext3 and have never had such issues.