On May 13 2015, Maxim Kostrikin wrote:
> I think the only reason for bigger max-obj-size is a db size. But 62.8
> MiB is considerably small. I have a setup with 10Gb+ of sqlite DB and
> it works, I guess the cons of bigger max-obj-size is multicore
> processing. If block is big, then s3ql should w
>
> No, what I meant was that I argued to use a bigger max-obj-size because I
> could not see deduplication happening with storing of movies and because
> the download granularity argument was not the case. You replied why not.
> The output of s3qlstat was my response.
>
>>
>> I think the only
On Tuesday, May 12, 2015 at 8:34:00 PM UTC+2, Nikolaus Rath wrote:
>
> On May 12 2015, Hans Reinders > wrote:
> > On Tuesday, April 21, 2015 at 2:58:29 AM UTC+2, Nikolaus Rath wrote:
> >> > is it possible / advisable to increase the max-obj-size to a very
> >> > high value (say 1GB)? Because
On May 12 2015, Hans Reinders wrote:
> On Tuesday, April 21, 2015 at 2:58:29 AM UTC+2, Nikolaus Rath wrote:
>> > is it possible / advisable to increase the max-obj-size to a very
>> > high value (say 1GB)? Because it will be only for backing up, the
>> > download granularity argument isn't the ca
On Tuesday, April 21, 2015 at 2:58:29 AM UTC+2, Nikolaus Rath wrote:
>
> On Apr 20 2015, Hans Reinders > 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
> > val
On Apr 20 2015, Hans Reinders 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
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)? Because it will be only for backing up, the download
granularity argument isn't the case. It also seems to me deduplication