You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yu Li (Jira)" <ji...@apache.org> on 2019/11/23 07:03:00 UTC

[jira] [Resolved] (FLINK-14877) Enable FRocksDB to optimize performance via options when bounding total memory

     [ https://issues.apache.org/jira/browse/FLINK-14877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yu Li resolved FLINK-14877.
---------------------------
    Resolution: Implemented

Closing issue as implemented since the relative PR for frocksdb is already merged.

> Enable FRocksDB to optimize performance via options when bounding total memory
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-14877
>                 URL: https://issues.apache.org/jira/browse/FLINK-14877
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Yun Tang
>            Assignee: Yun Tang
>            Priority: Major
>             Fix For: 1.10.0
>
>
> Currently, as we plan to keep base on RocksDB-5.17.2 and cherry-pick write-buffer manager related rocksJava commits to FRocksDB. Options below are recommend when bounding the total memory. 
> {code:java}
> tableConfig.setCacheIndexAndFilterBlocksWithHighPriority(true);
> tableConfig.setPinTopLevelIndexAndFilter(true);
> {code}
> However, RocksDB-5.17.2 does not include these java API. But luckily, these features are already implemented on RocksDB's native code. Cherry pick https://github.com/facebook/rocksdb/pull/4589 with only updates on java side should be enough.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)