> Optionally, you can hook up a custom compression algorithm. For example, Google Snappy offers even better performance than Brotli for the cost of worse compression ratios. ZSTD by Facebook is also worth checking out.
(...)
> The great news is that support for custom cache compression algorithms has recently been merged into the Rails main branch. But it may take a while before it’s available in a production Rails release.
Upcoming in Rails 7.1, you can specify a custom compressor for your cache, out of the box. See the `:compressor` option of `ActiveSupport::Cache::Store.new`:
Important to understand about Brotli vs. other compression is that Brotli has been pretrained with HTML/CSS/JS code. It efficiently compresses English text and source code, especially small files, due to its static dictionary.
8 comments
[ 3.3 ms ] story [ 23.4 ms ] threadhttps://raw.githubusercontent.com/facebook/zstd/v1.3.4/doc/i...
> Optionally, you can hook up a custom compression algorithm. For example, Google Snappy offers even better performance than Brotli for the cost of worse compression ratios. ZSTD by Facebook is also worth checking out.
(...)
> The great news is that support for custom cache compression algorithms has recently been merged into the Rails main branch. But it may take a while before it’s available in a production Rails release.
https://api.rubyonrails.org/v7.1/classes/ActiveSupport/Cache...
https://chromium.googlesource.com/external/font-compression-...
There are other factors that make Brotli good, but this is good to understand when dealing with web frontends.