Closed WenyXu closed 1 week ago
The recent changes focus primarily on updating the compression method used throughout the codebase. Specifically, the compression mode switched from NoCompression
to Lz4
in various configurations and the TopicManager
implementation. This update should improve data storage efficiency and potentially enhance performance.
Files | Change Summary |
---|---|
src/common/meta/src/wal_options_allocator/kafka/topic_manager.rs |
Changed compression method from NoCompression to Lz4 in TopicManager . |
src/common/wal/src/config.rs |
Updated compression setting to Compression::Lz4 for DatanodeWalConfig and DatanodeKafkaConfig . |
src/common/wal/src/config/kafka/datanode.rs |
Modified compression setting in DatanodeKafkaConfig from NoCompression to Lz4 . |
src/common/wal/src/config/kafka/standalone.rs |
Changed compression setting in StandaloneKafkaConfig from NoCompression to Lz4 . |
In the rustling code where bytes align,
Lz4 now compresses, oh so fine.
FromNoCompression
we take a flight,
Data packed smaller, faster than light.
A hop, skip, and a leap so grand,
Our configurations stand hand in hand.
🐇✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 85.01%. Comparing base (
849e0b9
) to head (13f71f3
). Report is 5 commits behind head on main.
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
Switch the default compression algorithm to LZ4 to reduce WAL size
Checklist
Summary by CodeRabbit
New Features
NoCompression
toLz4
across all configurations for improved data handling efficiency.Improvements