You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kukushkin (Jira)" <ji...@apache.org> on 2021/09/17 04:51:00 UTC

[jira] [Closed] (IGNITE-15460) Incorrect "Set max direct memory size" suggestion

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

Alexey Kukushkin closed IGNITE-15460.
-------------------------------------
    Ignite Flags:   (was: Docs Required,Release Notes Required)

> Incorrect "Set max direct memory size" suggestion
> -------------------------------------------------
>
>                 Key: IGNITE-15460
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15460
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.10
>            Reporter: Alexey Kukushkin
>            Priority: Major
>
> Ignite always outputs this performance suggestion on startup:
> {{Set max direct memory size if getting 'OOME: Direct buffer memory' (add '-XX:MaxDirectMemorySize=<size>[g|G|m|M|k|K]' to JVM options)}}
>  
> That is incorrect since:
>  * The Ignite [Memory and JVM Tuning|https://ignite.apache.org/docs/latest/perf-and-troubleshooting/memory-tuning#memory-and-jvm-tuning] page suggests NOT to explicitly set the {{MaxDirectMemorySize}} (unless native persistence is used but in this case set it to {{walSegmentSize * 4}}). Not setting {{MaxDirectMemorySize}} seems the right default option since in this case JVM would choose the most appropriate default size.
>  * Increasing direct memory size when getting OOME for direct memory seems too obvious to always print this information.



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