You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Tang (Jira)" <ji...@apache.org> on 2022/06/01 14:26:00 UTC

[jira] [Commented] (FLINK-27841) RocksDB cache miss increase in 1.15

    [ https://issues.apache.org/jira/browse/FLINK-27841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544932#comment-17544932 ] 

Yun Tang commented on FLINK-27841:
----------------------------------

[~Feifan Wang] The cache miss should be related with the frequency of data flush and compaction, could you check whether the behavior is the same as before after bumping Flink version.

> RocksDB cache miss increase in 1.15
> -----------------------------------
>
>                 Key: FLINK-27841
>                 URL: https://issues.apache.org/jira/browse/FLINK-27841
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / State Backends
>    Affects Versions: 1.15.0
>            Reporter: Feifan Wang
>            Priority: Major
>         Attachments: image-2022-05-31-00-21-49-338.png, image-2022-05-31-00-22-45-123.png
>
>
> I run same job with 1.12.2 and 1.15.0 , find that cpu busy much higher than 1.12. After careful comparison, I find higher cache miss in 1.15. But block cache size is same. Is this as expected ?
> I know RocksDB version in 1.15 is 6.20.3 and 1.12 is 5.17.2, is this just caused by different versions of RocksDB ?
> !image-2022-05-31-00-21-49-338.png|width=599,height=146!
> !image-2022-05-31-00-22-45-123.png|width=594,height=175!
> test information:
> job type : regular join
> per record size : 1000 bytes
> parallelism : 160
> TaskManager memory : 32G
> num of TaskManager : 10



--
This message was sent by Atlassian Jira
(v8.20.7#820007)