Hi Colin, Thanks for the reply.
The backup is a flat-file dataset containing assorted documents, videos, and audio files. I am trying to assess my initial costs, since I started with you guys very recently, before I send my initial backup over the wire; I am running it in a dry-run mode at the moment. The raw size of the dataset is 2.3TB running on a RAIDZ2 volume consisting of 4x4TB WD Red NAS drives (SATA3), 16GB of buffered ECC RAM, and an i3-4360/3.70GHz CPU. Once the initial backup is sent, there will be little overall change in the data (less than 0.5-1% change daily). Most of the change will be in the folders that deal with my business documents, unless a family video or two gets uploaded by my wife. Does this information help? Regards, Seth > On Aug 23, 2017, at 4:55 PM, Colin Percival <cperc...@tarsnap.com> wrote: > > Hi Seth, > > On 08/22/17 18:35, Seth P. Garrepy wrote: >> I am getting started with Tarsnap and had a general question about the >> development roadmap. I am liking Tarsnap so far, and I’m glad I found you >> all. I searched through the listserv archives, and didn’t see any reference >> to multithreading support. Are there any plans to parallelize tarsnap to >> improve performance on systems with lower clock rates but several logical >> cores? On my Haswell i3 FreeNAS box, it feels like tarsnap is stuck in 2nd >> gear! > > I've considered taking steps to use multiple CPUs, but it has never seemed > that CPU power was likely to be much of a bottleneck compared to disk I/O > and networking. Can you provide some more details about your usage pattern? > e.g., what sort of data are you archiving and how much of it changes between > archives? > > -- > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid