4 ms·
Nothing you’ve described there wasn’t possible with spinning disks storing large data sets. In fact if anything, ZFS is ideally suited to exactly that scenario.
by laumars 5y ago
Nothing you’ve described there wasn’t possible with spinning disks storing large data sets. In fact if anything, ZFS is ideally suited to exactly that scenario.
- b112 5y agoI assure you, rsync can tank a highly tuned db environment. 'updatedb', which updates the db 'locate' uses under linux, running in its cron, can cause issues. It all depends upon how much headroom you have, the type of io activity, etc. I've operated systems under consistent 80% io load with massive datasets at the time, under spinning disks. Running rsync would be madness on such a system. I know. I only did it once.
- whitepoplar 5y agoThey never said they were using rsync on their datasets. They're likely using ZFS snapshots.
- ComodoHacker 5y agoLet me guess, your system hadn't ionice back then?
- b112 5y agoionice works only on some elevators, and worked on fewer a decade ago. As well, ionice doesn't help with this degree of load.
- deleted 5y ago[deleted]
- laumars 5y agoThe article specifically said they were doing snapshots because you cannot rsync on live datasets. They’re doing it correctly and would still be doing it correctly if they were on spinning disks. ZFS is designed exactly for these types of operations.