I understand the need for independent fiber ISPs. But are gigabit speeds really necessary? For me, a 300 Mbps connection is way more than enough for a four-person family.
That's a bit more than I have (Starlink), but anytime a kid is downloading a big Steam game or big ISO file or something, everything else slows to a crawl. I also occassionally rsync large directories to/from cloud storage and that can also saturate. I've tried setting rules/priorities but it's a constant game of whack-a-mole
> I also occasionally rsync large directories to/from cloud storage and that can also saturate
Just offering some advice if you aren't aware. If you are, freely ignore. (And if you have advice in return I'd love to hear!)For convenience, the rclone tool is nice for most cloud storage like google and stuff that make rsync annoying[0]
rsync also offers compression[1], and you might want to balance it depending if you want to be CPU bound or IO bound. You can pick the compression and level, with more options than just the `-z` flag. You can also increase speed by not doing the checksum, or by running without checksum and then running again later with. Or some intervaling like daily backups without and monthly you do checksums.
If you tar your files up first I have a function that is essentially `tar cf - "${@:2}" | xz -9 --threads $NTHREADS --verbose > "${1}"` which uses the maximum `xz` compression level. I like to heavily compress things upstream because it also makes downloads faster and decompression is much easier than compression. I usually prefer being compute bound.
Also, a systemd job is always nice and offers more flexibility than cron. It's what's helped me most with the wack-a-mole game. I like to do on calendar events (e.g. Daily, Weekly) and add a random delay. It's also nice that if the event was missed because the machine was off it'll run the job once the machine is back on (I usually make it wait at least 15 minutes after machine comes online).