[SERVER-28442] Add support for lz4 wire protocol compression Created: 23/Mar/17 Updated: 30/Jul/19 Resolved: 30/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Chad Kreimendahl | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | Dev Tools 2019-08-12 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
If you're considering zlib for compression (with existing snappy), you may be better off considering lz4. It's substantially faster at compression and gets very close to snappy in terms of overall ratios. In some basic tests we've done for in-memory compression, lz4 is the only one of the 3 that appears to be capable of feeding data at line speed without recognizable latency. We get 9:1 compression out of snappy and about 7.5:1 out of lz4. However, our systems compress with lz4 at least twice as fast, in memory. I'd be happy to run some additional tests... and would love to see lz4 as a compression option everywhere. (lz4 file compression request coming soon) Relates to: |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 30/Jul/19 ] |
|
Hi sallgeud - Thanks for filing this ticket. We ended up going a different direction and integrating Zstandard for MongoDB 4.2 in |
| Comment by Kelsey Schubert [ 23/Mar/17 ] |
|
Hi sallgeud, Thanks for the feature request, I've assigned it to the Platforms Team for consideration. Please continue to watch for updates. Kind regards, |