Live data from Hacker News

Tarsnap performance issues in late March, most of April

mail.tarsnap.com

71–80 of 116 posts

Re: Tarsnap performance issues in late March, most of April

#71
post #51
post #29

Earlier quoted context omitted.

But its not cheap, which was my point. 100GB of storage costs: $300/year at tarsnap $36/year at S3

How much do you save after dedublication? Tar-snap could be a lot cheaper if you do frequent backups or you often change little in huge files.

Backup tools like attic (which I use) include automatic deduplication. There are surely minor differences in implementation, but tarsnap isnt the only implementation of deduplicating backup.

Re: Tarsnap performance issues in late March, most of April

#72
post #57

Earlier quoted context omitted.

You seem to have misunderstood me. I didn't suggest you should write your own encryption tool. There are numerous open source tools for creating encrypted backups, some do deduplication first too. If the tool doesn't happen to support remote storage, a simple rsync or scp fills that part. Literally the only thing unique about this service is the use of the term picodollars and the single individual it's all reliant o…

It's the dropbox discussion all over again. We know how that turned out, don't we?

Would you care to elaborate?

Re: Tarsnap performance issues in late March, most of April

#76
post #47

Earlier quoted context omitted.

Use the following shell command to decide when to run cron jobs. echo $((RANDOM % 60)) It's not a CSPRNG, but good enough for this kind of load balancing!

Or schedule your cron job for :00, but add "sleep `jot -r 1 0 3600` &&" to the start of the command. (jot is a BSDism, but I assume you can do the same with GNU seq.)

sleep $[RANDOM/3600] works everywhere without requiring jot/seq etc. on BSD/Mac/Linux.

Re: Tarsnap performance issues in late March, most of April

#77
post #74

Earlier quoted context omitted.

Threads

Too much overhead. Also, concurrent systems are actively malicious.

I don't believe that you have too many active connections for threading to work. Passive connections can be handled by a single or small number of threads. Modern Linux on modern hardware has no problem with many thousands of threads and the overhead is minimal in $$$ compared to the time you wasted debugging a scheduling problem.

As for concurrent systems being harmful, you just have to design your program for threading in mind. Minimize shared state and be very careful when you can't.

Re: Tarsnap performance issues in late March, most of April

#78
post #69
post #56

Earlier quoted context omitted.

Tarsnap isn't intended to be used as one-time backup like that, and it's super expensive if used that way. It's very cheap when used to backup (almost) the same 4GB for 1000 days in a row, which is what a lot of people/businesses need for their backup solutions.

It's not one time, I'd be incrementally writing updates to the disks. With a raspberry pi or something, the power costs are near negligible.

Rough estimate here:

If you upload 4tb in a year, that's 333.33gb/month

So for tarsnap that equals

- $1k/year in data transfer charges (4000gb * $0.25 transfer charge * 12 months)

- $83/month per month of data (333gb * $0.25 storage cost/month)

- $6.4k/year for the first year ($83 * 78 cumulative months in a year)

So $7.4k for 12 months resulting in 4tb

If usage stays the same each year will add $12k to the incremental yearly cost

Re: Tarsnap performance issues in late March, most of April

#79

Earlier quoted context omitted.

Or schedule your cron job for :00, but add "sleep `jot -r 1 0 3600` &&" to the start of the command. (jot is a BSDism, but I assume you can do the same with GNU seq.)

sleep $[RANDOM/3600] works everywhere without requiring jot/seq etc. on BSD/Mac/Linux.

s/\//%/ I assume?

Re: Tarsnap performance issues in late March, most of April

#80
post #57

Earlier quoted context omitted.

It's the dropbox discussion all over again. We know how that turned out, don't we?

Would you care to elaborate?

When Drew first do a "Show HN" [0] (before it was a thing, actually), there were a lot of response about how it doesn't do anything new that couldn't be already done by a technical inclined person (see the first two top comments in the posts).

To make a comparison with tarsnap, while it's probably possible to do encrypted backup manually with a combination of shellscript and such, there are just too many moving pieces that can go wrong. Where do you store the backup? Someone mentions S3, but even managing backup on S3 with deduplication is not something trivial, and managing the encryption process is definitely not something most of us can say with confident we won't mess up. I can imagine a thousand way that I encrypt something, then unable to decrypt it back.

And then maintenance is also an issue, if I'm using a set of OSS tools, I would have to make sure the tool is being maintained, and to follow any potential disclosure on bug/ updates etc. With Tarsnap, I know I will get an email from cperciva if something comes up.

[0]: https://news.ycombinator.com/item?id=8863

Post reply on HN