dtgreene: One use case for this fast compression is the Linux kernel's zram module, which creates a compressed ramdisk that can be used as swap space.
Which i've used in some tiny VM distros for servers, it was rather cool... of course the server had very low loads so having 64Mb of ram was sorta just workable at the time.
Although for Zram, i'd hope it does quick compression for swapping, then if it's slow and nothing's happening, it goes back and recompresses blocks to make more room, either with just better algorithms, or at higher compression settings. I was really curious why MS never implemented anything like that... between 98 and XP...
dick1982: i used ramdisk once for temp files and browser caches.
that was rather pointless and annoying. corrupted temp files made it impossible to restart until i went into safemode and change the temp directories back. having limited browser cache forced me to clear it more often. and isn't using ramdisk for swapping files considered worse than just letting your RAM work normally?
In raw speed, yeah probably... but even simple compression on data tends to yield very good compression. If you set 100MB aside for your swap drive, it could hold far more than 100MB, on the other hand it won't hold less than 100MB... so it's sorta free Ram, unless you're under a heavy load. But unless you're doing something like recompiling the Linux kernel, or running a huge server that requires hundreds of megabytes for indexing... then zRAM may work better...
It's a better solution than doing a regular swap device. It's often said, the slowest CPU and memory speed is still faster than the fastest hard drives for sending/retrieving information.