[SERVER-49405] Ability to pass --fast flag to zstd Created: 09/Jul/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Oliver Yeh | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
According to https://github.com/facebook/zstd "zstd 1.4.5 --fast=7 is much faster than snappy at same compression level. But right now, there is no way to tell mongodb to use zstd at --fast=7"
Related |
| Comments |
| Comment by Matt Parlane [ 20/Aug/21 ] | ||||
Noooo!!! Without --fast, Zstd is not as good as Snappy. With --fast it immediately becomes a no-brainer. Surely this is doable? I understand --fast is just a negative compression number, why not just allow negative numbers in the command line switch? | ||||
| Comment by Alexander Gorrod [ 30/Apr/21 ] | ||||
|
We updated the fix version - but there is no change to the priority of this work - we still have this high on our priority list. |