[
https://issues.apache.org/jira/browse/IGNITE-28072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-28072:
---------------------------------------
Description:
By default, JVM stores perf-tracking file in /tmp, and /tmp is often on the
main FS in modern OS distros by default. As a result, this file is stored on a
real FS (on a disk). If the system experiences high disk I/O, writes to this
file may take a lot of time. And those writes do not allow the JVM to reach
safe points. The result is that JVM gets frozen.
Users themselves can configure the path so the file resides on a ram disk, but
we should have this (potentially dangerous for performance) functionality
disabled to have better default UX. Adding -XX:+PerfDisableSharedMem allows to
disable usage of that perf-tracking file.
> Add -XX:+PerfDisableSharedMem to default java options
> -----------------------------------------------------
>
> Key: IGNITE-28072
> URL: https://issues.apache.org/jira/browse/IGNITE-28072
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> By default, JVM stores perf-tracking file in /tmp, and /tmp is often on the
> main FS in modern OS distros by default. As a result, this file is stored on
> a real FS (on a disk). If the system experiences high disk I/O, writes to
> this file may take a lot of time. And those writes do not allow the JVM to
> reach safe points. The result is that JVM gets frozen.
> Users themselves can configure the path so the file resides on a ram disk,
> but we should have this (potentially dangerous for performance) functionality
> disabled to have better default UX. Adding -XX:+PerfDisableSharedMem allows
> to disable usage of that perf-tracking file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
