test(bench): add compression benchmark #3090
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's changed and what's your intention?
Introduce compression benchmark to compare the encode speed between block compression and stream compression.
Stream compression is helpful to better align block size in SSTs, which benefits the file cache system by reducing internal fragmentation.
Results
The uncompressed data is consists of (tables * pairs) encoded kv pairs:
vsize
is, the lower compression rate is. The compression rate should be higher with real-world workload. And the speed will be also faster.In conclusion, The larger each uncompressed entry size is, the smaller the speed difference is. And there is no obvious difference between compression rates.
Because L0 doesn't enable any compression algorithms, IMO, the extra compress time is bearable for compection only.
Checklist
./risedev check
(or alias,./risedev c
)Refer to a related PR or issue link (optional)
#198