EQUATE during decompression.
> If I have a .xz file (downloaded from the Internet) that needs 90 MB
> RAM to decompress, then I need to use those 90 MB no matter if
> that's nice or not, it's just critical.
>
> I am proposing to Lasse Collin to drop memory capping function
ssity to change it.
In short, some people find a default limit annoying and some other
people would find lack of default limit annoying. (And most people
probably don't care.) So the question is, which group will complain
more; obviously I cannot make everyone happy. At this point it starts to
On 2010-06-20 Matthias Andree wrote:
> Am 19.06.2010 15:41, schrieb Lasse Collin:
> > Perhaps FreeBSD provides a good working way to limit the amount of
> > memory that a process actually can use. I don't see such a way e.g.
> > in Linux, so having some method in the a
isks start to
become competitive, because the memory is accessed quite
randomly.
- Dictionary keeps the most recently processed uncompressed
data in a ring buffer. Using a dictionary bigger than the
uncompressed file is useless.
- Compressor memory usage is roughly 5-12 time
h barely qualifies as
> "extreme" in my eyes. "extreme" would be an order of magnitude
> (10x).
The option name isn't the greatest, I'm generally bad at naming things.
Time increase with "xz -2e" is around 10x comp
