agreed, I think there is something else going on here. test the write speed with another application, I doubt the drive actually maxes out at 40MB/s unless it’s severely fragmented or failing.
Comment on Data HDD with SSD catch drive
ShortN0te@lemmy.ml 3 weeks ago
40MB/s is very very low even for a HDD. I would eventually debug why it’s that low.
Yes it’s possible. FS like zfs btrfs etc. support that.
acosmichippo@lemmy.world 3 weeks ago
rambos@lemm.ee 3 weeks ago
Its the cheapest drive I could find (refurbished seagate from amazon), I thought thats the reason for being slow, but wasnt aware its that low. Im also getting 25-40 MB/s (200-320 Mbps) when copying files from this drive over network. Streaming works great so its not too slow at all. Is there better way of debugging this? What speeds can I expect from good drive or best drive?
Ill research more about BTRFS and ZFS, thx
acosmichippo@lemmy.world 3 weeks ago
can you copy files to it from another local disk?
rambos@lemm.ee 3 weeks ago
Yeah, but need to figure out how to see transfer speed using ssh. Sorry noob here :)
not_fond_of_reddit@lemm.ee 3 weeks ago
If you use scp (cp over ssh) you should see the transfer speed.
possiblylinux127@lemmy.zip 3 weeks ago
Btrfs doesn’t support using a cache drive
catloaf@lemm.ee 3 weeks ago
It’s probably a 5400rpm drive, and/or SMR. Both are going to make it slower.
Appoxo@lemmy.dbzer0.com 3 weeks ago
5.4k + smr would explain it at write but not at read.
Markaos@lemmy.one 3 weeks ago
In my very limited experience with my 5400rpm SMR WD disk, it’s perfectly capable of writing at over 100 MB/s until its cache runs out, then it pretty much dies until it has time to properly write the data, rinse and repeat.
40 MB/s sustained is weird (but maybe it’s just a different firmware? I think my disk was able to actually sustain 60 MB/s for a few hours when I limited the write speed, 40 could be a conservative setting that doesn’t even slowly fill the cache)