nsqio/nsq

nsqd: Use Klaus Post's compression libraries

Open

#1,484 创建于 2024年4月15日

在 GitHub 查看
 (5 评论) (1 反应) (0 负责人)Go (25,788 star) (2,898 fork)batch import
help wantedperf

描述

We would quite like to use compression with NSQ to save on data transfer costs, but the CPU impact is higher than we'd like. Our experiments have shown that Klaus Post's compression libraries perform much better than the standard library Deflate and Google's Snappy, with the sweet spot appearing to be level 3 flate compressing our traffic to about 25% of its original size, but only incurring a CPU cost equivalent to Snappy.

Would there be any interest in taking a PR that makes this change?

贡献者指南

技术栈
go
领域
backendperformance
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Go programmingunderstanding of nsqd codebaseknowledge of compression algorithms
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate the current compression implementation in nsqd, likely in the nsqd package. Review the linked compression library (github.com/klauspost/compress) and its flate/snappy compressors. Consider the benchmark results mentioned in the issue to validate performance gains. Discuss with maintainers on the issue thread about preferred approach and code guidelines.