I meant to mention them in my email as both of them are great options when
you don't mind sacrificing some compression for significant improvements in
compression and decompression speeds. These libraries are I/O bound when
saving to a hard drive unless you are using a very low powered processor.
snappy and lz4 are good algos to try too.
On Fri, Mar 27, 2015 at 8:55 AM, Maciej Fijalkowski
wrote:
> yeah I think putting gzip or something in the loop is A LOT easier :-)
>
> On Thu, Mar 26, 2015 at 6:29 PM, John Camara
> wrote:
> > Hi Fijal,
> >
> > To recap and continue the discussion from
yeah I think putting gzip or something in the loop is A LOT easier :-)
On Thu, Mar 26, 2015 at 6:29 PM, John Camara wrote:
> Hi Fijal,
>
> To recap and continue the discussion from irc.
>
> We already discussed that the stack id are based on a counter which is good
> but I also want to confirm th
Hi, It's worth adding lzop to the list, of compressors to test, as it's built
specifically to have a low CPU overhead, at the cost of some compression ratio.
http://www.lzop.org/
S++
On Thursday, March 26, 2015 11:29 PM, John Camara
wrote:
Hi Fijal,
To recap and continue the
Hi Fijal,
To recap and continue the discussion from irc.
We already discussed that the stack id are based on a counter which is good
but I also want to confirm that the ids have locality associated with the
code. That is similar areas of the code will have similar ids. Just to
make sure are not
