OP has discovered Tapirs exist.
this post was submitted on 10 Jun 2024
1129 points (98.8% liked)
Programmer Humor
19452 readers
147 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
Fun fact: tapir before defrag
I cannot help but see this as a diaper pattern…
Oh man, I knew I had seen this pattern somewhere.
Pro tip: Defragmenting only works on spinning drives because it puts the data nearer to the spindle so seek times are shorter. Solid-state drives wear out faster if you defragment them, since every write involves a little bit of damage.
I was about to throw hands, but then I learned something new about how SSDs store data in pre-argument research. My poor SSDs. I've been killing them.
No you didn‘t. All somewhat current operating systems do not defrag SSDs, they just run TRIM and it does not kill them.
Most modern OSeses do defragmentation on the fly and you don't really need to do it anymore.
Which makes me sad because I have so many memories of watching a disk defragmenter do its thing from my childhood.
Here's a little game I made because I missed it too. https://dbeta.com/games/webdefragger/
That was super cool.
Thanks. It was a silly toy, but it scratched an itch, and was good for at least one chuckle.
I loved watching disk defragmenter doing it‘s job as a kid. I miss it too!
real actually. definitely one of the most memorable progress bars. well, that and the bios update progress bar
Random reads are still slower than sequential in SSD. try torrenting for a year on SSD, then benchmark then defragment then benchmark. it will be very measureable difference. you may need some linux filesystem like XFS as im not sure if there is a way to defrag SSDs in windows.
That's because the drive was written to its limits; the defrag runs a TRIM command that safely releases and resets empty sectors. Random reads and sequential reads /on clean drives that are regularly TRIMmed/ are within random variance of each other.
Source: ran large scale data collection for a data centre when SSDs were relatively new to the company so focused a lot on it, plus lots of data from various sectors since.
I'm pretty sure running XFS defrag will defrag without trimming no matter the type of block device.
Edit: yea you might actually be right. I Played with my fstab too much years ago, and never thought of that untill now
I understood that XFS automatically mounted SSD's with XFS_XFLAG_NODEFRAG set? Is this not the case?
yea you might actually be right. I Played with my fstab too much years ago, and never thought of that until now
But does that flag affect manually running xfs_fsr?
According to the man(8) page, it will avoid touching any blocks that have the chattr -f flag set, which is XSR_XFLAGS_NODEFRAG... So I think if the docs are still accurate to the code, yes.
A lot of ifs in that assumption.
Pro tip: That tip has been obsolete for a long time now. Running the defragmentation tool on an SSD in Windows optimizes the drive (pretty much just running TRIM). It's not possible to defragment an SSD in Windows (maybe there is a way using some register hack but that's out of scope)
Defragging is about.... defragging: making the data contiguous (a continuous stream along one arc of the same radius) so it doesn't have to jump around.
well, defragging my ssd was the only thing that let me shrink the windows partition safely when i dualbooted... tho maybe thats just windows being funky
That kinda makes sense. Putting all the partition sectors together would probably make it easier to resize. But as standard maintenance it's like changing the oil on an electric car.
i see
Defragging an SSD on a modern OS just runs a TRIM command. So probably when you wanted to shrink the windows partition, there was still a bunch of garbage data on the SSD that was "marked for deletion" but didn't fully go through the entire delete cycle of the SSD.
So "windows being funky" was just it making you do a "defragmentation" for the purpose of trimming to prepare to partition it. But I don't really see why they don't just do a TRIM inside the partition process, instead of making you do it manually through defrag
load more comments
(1 replies)
You just don't want to do it regularly. It was an issue for a brief time when SSDs were new, but modern operating systems are smart enough to exclude SSDs from scheduled defrags.
All I could think of.
Ahh. TV shows before everything became political. Just two guys hating each other for very silly reasons completely unconnected to anything on earth.
Needs an /s
load more comments
(1 replies)
The tail is a different partition?
It's the SATA cable
This sounds like it could be right, but I don’t know enough about zebra tails.
Now it's a Z:\bra
It runs much faster now.
I thought zebras were solid state.
They're striped RAIDS, obviously.
Actually they're mostly water.
Well defraging liquid state sounds like a bad idea too.
Too many moving parts to be solid state. Maybe about 10 minutes after one dies.
Defragged cows. System files cannot be moved.
If they stand close enough and you scan them with a barcode scanner, they show up in the system as beef, but for only $0.21/per pound.
load more comments
(1 replies)
EXT4 watching NTFS solve its fragment problem by upgrading to SSDs instead of upgrading their allocation algorithm.
This is what south African zebras look like.
It's what they looked like, in the good old times.
Bruv this is #4 top lemmy post of the day... how did we get here
By defragging the zebra, duh
It's very relatable
view more: next ›