[MDEV-19108] [feature] [tokudb] Issue: #63 Add compression ratio statistics per FT Created: 2019-03-31  Updated: 2021-11-02  Resolved: 2021-11-02

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - TokuDB
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Anel Husakovic Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None

Epic Link: AliSQL patches

 Description   

TokuDB has status to expose the compression ratio:
 
    mysql> show global status like 'tokudb%COMPRESSION_RATIO';
    +---------------------------------------+----------+
    | Variable_name                         | Value    |
    +---------------------------------------+----------+
    | Tokudb_LEAF_NODE_COMPRESSION_RATIO    | 5.850260 |
    | Tokudb_NONLEAF_NODE_COMPRESSION_RATIO | 0.564453 |
    | Tokudb_OVERALL_NODE_COMPRESSION_RATIO | 4.528809 |
    +---------------------------------------+----------+
 
but this a global level ratio, and sometimes the users may be interested
in table level compression ratio.
 
This patch address this request by exposing FT level compresstion ratio
through information_schema.TokuDB_fractal_tree_info table. We add two
columns, leaf_compress_ratio and internal_compress_ratio, which indicate
the compression ratio of leaf nodes and internal nodes accordingly.
 
Limitations, the comppression ratio infos are maintained in memeory, and
will lost when server is restarted or ft get evicted from memory.
Maybe in future there infos will be persisted in ft file, when this feature
is accepted by PerconaFT upstream.

https://github.com/alibaba/AliSQL/commit/4ec960a375dc3757a0e8132503e761b2fb6f8f1f



 Comments   
Comment by Marko Mäkelä [ 2021-11-02 ]

TokuDB was removed in MDEV-19780.

Generated at Thu Feb 08 08:49:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.