You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Didar Shayarov (Jira)" <ji...@apache.org> on 2025/09/14 15:54:00 UTC
[jira] [Commented] (IGNITE-26356) Clarify recommendations for -XX:MaxDirectMemorySize in docs
[ https://issues.apache.org/jira/browse/IGNITE-26356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020171#comment-18020171 ]
Didar Shayarov commented on IGNITE-26356:
-----------------------------------------
[~shishkovilja] [~shishkov_ilja]
> Clarify recommendations for -XX:MaxDirectMemorySize in docs
> -----------------------------------------------------------
>
> Key: IGNITE-26356
> URL: https://issues.apache.org/jira/browse/IGNITE-26356
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 2.17
> Reporter: Didar Shayarov
> Assignee: Didar Shayarov
> Priority: Minor
> Labels: documentation, ise
> Fix For: 2.18
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Current documentation for memory tuning recommends setting -XX:MaxDirectMemorySize to walSegmentSize * 4 (if you use native persistance).
> This advice is misleading because the default limit for direct buffers is already equal to -Xmx. The formula may cause unnecessary OOME: Direct buffer memory errors and may mislead user to accidently decrease actual direct buffer size.
> There is also legacy todo in code (since at least 2020) questioning this recommendations.
> It is better to provide safer guidelines in docs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)