On 06/30/2014 10:22 PM, Brice Burgess wrote:
> I went ahead and used the --compress none flag to disable compression. I
> had to re-create the fileksystem to get it working (as it was previously
> mounted with LZMA compression, and thus rightly retains this setting
> upon remounting it).
It should not. What makes you think it retained the setting? Mounting
the (existing) file system with --compress <alg> should change the
compression of all new objects. There is no need to worry about
decompressing the old LZMA compressed objects, that only takes a small
amount of memory.
> Can anyone forsee issues running with --compress none? Obviously traffic
> is increased; but memory (and CPU) is tight on these small VMs. Would
> bzip/zlib be a better option?
Yes. Both require orders of magnitude less memory than lzma, so I'd
definitely try one of those instead of not compressing at all.
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 s3ql+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
