It depends what you’re optimising for. If you want a single (relatively small) download to be available on your HDD as fast as possible, then your current setup might be better (optimising for lower latency). However, if you want to be maxing out your internet speeds at all time and increase your HDD speeds by making the copy sequential (optimising for throughput), then the setup with the catch drive will be better. Keep in mind that a HDD’s sequential write performance is significantly higher than its random write performance, so copying a large file in one go will be faster than copying a whole bunch of random chunks in a random order (like torrents do). You can check the difference for yourself by doing a disk benchmark and comparing the sequential vs random writes of your drive.
Comment on Data HDD with SSD catch drive
rambos@lemm.ee 2 months agoBut that would first download to SSD, then move to HDD and then become available (arr import) on jellyfin server, making it slower than not using SSD. Am I missing something?
Maxy@lemmy.blahaj.zone 2 months ago
rambos@lemm.ee 2 months ago
Thank you. The files I download are usually 5-30 GB size. I don’t want to max out my internet speed, I just want to get the files in media library ASAP after requesting download manually (happens maybe few times a week)
It makes sense, Ill test sequential and random write performance and maybe even test it since I have the hardware available.
At first I wasn’t aware that my speed is super low for HDD, therefore I was looking for some magic solution with SSD speeds and HDD storage that might not even exist. I have to do more testing for sure
braindefragger@lemmy.world 2 months ago
Is that not what you asked for?
rambos@lemm.ee 2 months ago
Well yes, but I was hoping files can be available (imported to media server) before they are moved to HDD. Import is not possible from incomplete directory if I understood that correctly (*arr stack)
catloaf@lemm.ee 2 months ago
You would have to add both directories to your library.