You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2026/03/05 13:48:00 UTC
[jira] [Updated] (IGNITE-28075) Make writeBufferSize for RocksDB-based log storage configurable
[ https://issues.apache.org/jira/browse/IGNITE-28075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Puchkovskiy updated IGNITE-28075:
---------------------------------------
Description:
Currently, it's hard-coded to 64Mb, but for some workloads it might be inoptimal. For instance, when doing huge puts of 100Mb each, it makes sense to set this to 256Mb.
This should be configurable via our configuration framework, but, as we are going to switch to Segstore, it doesn't make sense to add a public property so specific to RocksDB-based implementation. For this reason, it seems better to add it as an (undocumented) system property in node configuration.
> Make writeBufferSize for RocksDB-based log storage configurable
> ---------------------------------------------------------------
>
> Key: IGNITE-28075
> URL: https://issues.apache.org/jira/browse/IGNITE-28075
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> Currently, it's hard-coded to 64Mb, but for some workloads it might be inoptimal. For instance, when doing huge puts of 100Mb each, it makes sense to set this to 256Mb.
> This should be configurable via our configuration framework, but, as we are going to switch to Segstore, it doesn't make sense to add a public property so specific to RocksDB-based implementation. For this reason, it seems better to add it as an (undocumented) system property in node configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)