You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "weiming (Jira)" <ji...@apache.org> on 2024/08/15 11:23:00 UTC
[jira] [Commented] (HDDS-11230) Make RocksDB cache configurable in Ozone Manager
[ https://issues.apache.org/jira/browse/HDDS-11230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873895#comment-17873895 ]
weiming commented on HDDS-11230:
--------------------------------
[~weichiu]
I am interested in this issue, could you assign it to me?
> Make RocksDB cache configurable in Ozone Manager
> ------------------------------------------------
>
> Key: HDDS-11230
> URL: https://issues.apache.org/jira/browse/HDDS-11230
> Project: Apache Ozone
> Issue Type: Improvement
> Components: OM
> Reporter: Duong
> Priority: Major
>
> Ozone Manager's performance heavily depends on RocksDB performance. RocksDB cache plays an important role in RocksDB's read performance, especially when a client has to host OM's metadata in not-so-fast hardware.
> Today, OM RocksDB cache is fixed at 256MB (see DBProfile), this is unreasonable because the cache size should depend on the client use-case, i.e. how big is their active key space. For example, if a client always has 1M of hot keys daily, and each key metadata is 1kb, having a cache size of 1GB makes a lot of sense.
> Ref:
> * [https://github.com/facebook/rocksdb/wiki/Block-Cache]
> * [https://github.com/facebook/rocksdb/wiki/Performance-Benchmarks]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org