You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jufang He (Jira)" <ji...@apache.org> on 2024/02/06 08:40:00 UTC
[jira] [Commented] (FLINK-34386) Add RocksDB bloom filter metrics
[ https://issues.apache.org/jira/browse/FLINK-34386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814681#comment-17814681 ]
Jufang He commented on FLINK-34386:
-----------------------------------
[~pnowojski] could you take a look at this?
> Add RocksDB bloom filter metrics
> --------------------------------
>
> Key: FLINK-34386
> URL: https://issues.apache.org/jira/browse/FLINK-34386
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Affects Versions: 1.18.0
> Reporter: Jufang He
> Priority: Major
>
> In our production environment, with RocksDB bloom filter enabled, the performance optimization effect on task state reading is obvious. However, there is a lack of usage metrics for bloom filter, If these Metrics are reported via Metrics reporter, it is easy to monitor the effectiveness of bloom filter optimization.
> And these metrics are available from rocksdb Statistics:
> BLOOM_FILTER_USEFUL: times bloom filter has avoided file reads.
> BLOOM_FILTER_FULL_POSITIVE: times bloom FullFilter has not avoided the reads.
> BLOOM_FILTER_FULL_TRUE_POSITIVE: times bloom FullFilter has not avoided the reads and data actually exist.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)