On Apr 20 2015, Hans Reinders <[email protected]> wrote: > Hello, > > When using s3ql for backup purpose of files (movies) with size of 1 - 2 GB, > is it possible / advisable to increase the max-obj-size to a very high > value (say 1GB)?
Possible yes. Advisable I'm not sure. > Because it will be only for backing up, the download > granularity argument isn't the case. It also seems to me deduplication will > not be an argument to use the default max-obj-size of 10MB. Why not? > Main reason for this question is the fact that a TB or more of this kind of > files results in hundreds of thousands of objects with the default > max-obj-size of 10MB. Why is this an issue? > The backend used will be OpenStack Swift (Hubic). Are you planning to use the experimental patches from https://bitbucket.org/nikratio/s3ql/issue/132/, or do you have a method to make it work out of the box? 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.
