On Jun 19 2016, Brandon Orwell <[email protected]> wrote:
> Right, but in this case, what's the difference?
You should not deviate from the default without good reason. So if you
think it doesn't make a difference, that's an argument for going with
the default.
> Does having a. Lower size help ensure there
> are no issues in the case of an interrupted transfer?
Yes, among other things.
> And it would matter because if we're talking 45TB, which is what is
> being uploaded, and we had to recover from a catastrophic failure, the
> amount of GETs to recover and amount of PUTs to store in any case
> wouldbe high if the object size is low. So the math here is its very
> expensive if there are that many objects.
I highly recommend that you actually *do* the math, instead of relying
on your intuition of what the result will be.
Suppose you use standard storage. Transferring 45 TB costs you about
$0.090/GB * 45 TB = $ 4147. With the default block size, you need
4718592 GET requests, costing you $ 1.887 ($ 0.004 for 10,000
requests). In other words, in the best case you will save less than $ 2
out of $ 4149.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
