[MDEV-22310] Support zstd Compression algorithm for IO Created: 2020-04-20 Updated: 2023-12-21 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Protocol |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | Diego Dupin | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 4 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
GoalServer support zlib library for compression. MySQL implement that in 8.0. New variables[Compression_algorithm|https://dev.mysql.com/doc/refman/8.0/en/server-status-variables.html#statvar_Compression_algorithm] : The name of the compression algorithm in use for the current connection to the server Protocol changeNew capability CLIENT_ZSTD_COMPRESSION_ALGORITHM (1UL << 26) indicate supporting zstd algorithm. (enable when global variable protocol-compression-algorithms contains zstd). Handshake Response Packet has a new "compress_level" value
No dictionnary is used in MySQL implementation, but dictionary with zstd benchmarks generally improve encryption/decryption time drastically for small amount of data. Some verification might be done to see if that this can be applicable to MariaDB exchanges |
| Comments |
| Comment by Vladislav Vaintroub [ 2020-04-20 ] |
|
If I can be allowed a sceptical remark.
As for dictionary , what can be added to it except "\03def"? |