视频1 视频21 视频41 视频61 视频文章1 视频文章21 视频文章41 视频文章61 推荐1 推荐3 推荐5 推荐7 推荐9 推荐11 推荐13 推荐15 推荐17 推荐19 推荐21 推荐23 推荐25 推荐27 推荐29 推荐31 推荐33 推荐35 推荐37 推荐39 推荐41 推荐43 推荐45 推荐47 推荐49 关键词1 关键词101 关键词201 关键词301 关键词401 关键词501 关键词601 关键词701 关键词801 关键词901 关键词1001 关键词1101 关键词1201 关键词1301 关键词1401 关键词1501 关键词1601 关键词1701 关键词1801 关键词1901 视频扩展1 视频扩展6 视频扩展11 视频扩展16 文章1 文章201 文章401 文章601 文章801 文章1001 资讯1 资讯501 资讯1001 资讯1501 标签1 标签501 标签1001 关键词1 关键词501 关键词1001 关键词1501 专题2001
CompressingLargeDataSetsinRedisWithGzip
2020-11-09 13:23:51 责编:小采
文档


Compressing Large Data Sets in Redis With Gzip: When publishing it, the post dropped the quote and my comments. A long post analyzing different scenarios of compressing data stored in Redis using Gzip: Year and a half ago, I was working wi

Compressing Large Data Sets in Redis With Gzip:

When publishing it, the post dropped the quote and my comments.

A long post analyzing different scenarios of compressing data stored in Redis using Gzip:

Year and a half ago, I was working with a software that used Redis as a buffer to store large sets of text data. We had some bottlenecks there. 
One
of them was related to Redis and the large amount of data, that we had there
(large comparing to RAM amount). Since then, I’ve wanted to check if using
Gzip would be a big improvement or would it be just a next bottleneck (CPU).
Unfortunately I don’t have access to this software any more, that’s why I’ve
decided to create a simple test case just to check this matter.

If what’s important is the speed, I think algorithms like snappy and lzo are a better fit. If data density is important, then Zopfli is probably a better fit.

Original title and link: Compressing Large Data Sets in Redis With Gzip (NoSQL database?myNoSQL)

下载本文
显示全文
专题