I get....that's the icybox attached to an rpi4 with a pair of (recently purchased) https://www.amazon.co.uk/dp/B07D9C7SQH? ... asin_title attached as simple ext4 drives. Took hours (days) to rsync them but once done, not much changes, so not a problem. Note what @thlgrol mentioned about ethernet being the bottleneck: my rsync backup scripts do tend to use the "--bwlimit" option to leave bandwidth free for normal operations.
It revolves around identifying your use case. Mine won't be yours. Most responsive we need our NAS to be is to play 720p(*) video. Nothing else matters as long as it completes its backup before the next scheduled backup commences - and 1Gb intranet isn't flooded.
(*) None of our displays warrant HD so I do a one-off transcode of them down to 720p but with streaming that's becoming a thing of the past.
If I want really responsive, I use "tmpfs" but that's a niche use case (I do a lot of compiling).
Code:
foo@pi19:~ $ lsscsi[0:0:0:0] disk USB SanDisk 3.2Gen1 1.00 /dev/sdc #timeshift thumbdrive (for OS)[1:0:0:0] disk ST4000DM 004-2U9104 0106 /dev/sda #icybox[1:0:0:1] disk ST4000DM 004-2U9104 0106 /dev/sdb #icyboxfoo@pi19:~ $ sudo hdparm -t /dev/sda/dev/sda: Timing buffered disk reads: 380 MB in 3.00 seconds = 126.51 MB/sec foo@pi19:~ $ sudo hdparm -t /dev/sdb/dev/sdb: Timing buffered disk reads: 444 MB in 3.03 seconds = 146.29 MB/sec It revolves around identifying your use case. Mine won't be yours. Most responsive we need our NAS to be is to play 720p(*) video. Nothing else matters as long as it completes its backup before the next scheduled backup commences - and 1Gb intranet isn't flooded.
(*) None of our displays warrant HD so I do a one-off transcode of them down to 720p but with streaming that's becoming a thing of the past.
If I want really responsive, I use "tmpfs" but that's a niche use case (I do a lot of compiling).
Statistics: Posted by swampdog — Wed Dec 18, 2024 5:59 pm