On May 13 2015, Maxim Kostrikin <[email protected]> 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 wait till next big block
> will be copied to start using next core. Or not?
That's correct.
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.
