Re: Features

On Tue, 25 Nov 1997, Dancer wrote:

> We average about 2%. Mostly, my qualms about memory usage come from the requirements of
> having the uncompressed object and the compressed object in memory simultaneously during
> compression. Essentially (for safety) you take two buffers of the size of the original
> object.

With lzo this will not be nessassary if implimented right..

>
> Now, you can do it in pieces...I did it when I implemented the streaming compression on
> top of zlib, which bypasses the memory hog problems, but there are a couple minor
> restrictions on how many bytes you can feed in per compression call, and how many on a
> decompression call. (multiples of 3 and 4). 24 works well as an input size and 32 as an
> output size. Perhaps some of those might get relaxed since mostly they involved integrity
> hashing for encryption. I'll pull out the code and see if I can't code a compression
> routine into sparent 1.4. I know _I_ could use it, and then I don't have to shoehorn it
> into Squid. Someone else can do that later.
>
> D
>
Look at lzo..
Received on Mon Nov 24 1997 - 07:07:44 MST