Just a feature request,
Would be nice to have nginx support for LZ4 (like gzip static
support), to have an alternative compression method built in…
On Monday 20 February 2012 04:34:24 Ryan B. wrote:
Just a feature request,
Would be nice to have nginx support for LZ4 (like gzip static
support), to have an alternative compression method built in…
Are there any browser that supports it?
wbr, Valentin V. Bartenev
sorry, I assumed the decryption would’ve been done by nginx rather
than the browser
On Tuesday 21 February 2012 15:32:28 Ryan B. wrote:
sorry, I assumed the decryption would’ve been done by nginx rather
than the browser
It seems that you suggest:
read a lz4 file or stream -> decode lz4 -> encode gzip -> serve to
browser
instead of:
read a gzip file or stream -> serve to browser
…so, where’s the profit?
wbr, Valentin V. Bartenev
You could use BTRFS with its “compression=lzo” mount-option, available
since Linux 2.6.38. [1]
I don’t know if LZ4 and Snappy will integrated into Linux 3.4, but you
can try them out pulling changes from
[4] Public Git Hosting - linux-2.6/btrfs-unstable.git/summary
(dev/compression-squad branch)
Compared to LZO, LZ4 doesn’t show any measurable performance increase
for read-only access.
–
Mark
[1] https://btrfs.wiki.kernel.org/
[2] btrfs: Add lzo compression support [LWN.net]
[3]
Btrfs LZO Compression Performance - Phoronix
[4b]
http://www.mail-archive.com/[email protected]/msg14884.html
Am 21. Februar 2012 12:32 schrieb Ryan B. [email protected]:
read a lz4 file or stream → serve to browser
Can I also request LZ4 compression be a supported feature for direct
delivery to a browser ? As a provider this means less overhead of a
compressed stream on each connection, meaning that there’s less of a
bandwidth vs. CPU tradeoff.
I’ve begun requesting different browsers support this natively as well.
The real question I suppose is: How did gzip come to be used ? With the
performance differences in speed and compression I envision a shift to
LZ4.
Thoughts ?
Posted at Nginx Forum: