[
https://issues.apache.org/jira/browse/IOTDB-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574012#comment-17574012
]
Jialin Qiao commented on IOTDB-4013:
------------------------------------
The memory that a Java process occupied not only contains the heap memory, but
also others, refer to
[https://stackoverflow.com/questions/36872551/relation-between-memory-host-and-memory-arguments-xms-and-xmx-from-java|https://stackoverflow.com/questions/36872551/relation-between-memory-host-and-memory-arguments-xms-and-xmx-from-java.]
We could adjust the JVM parameter to reduce the memory usage. Could reach to
70M when starting.
https://apache-iotdb.feishu.cn/docx/doxcnrug9b31OFJUSY5v5sXCyGb
> Set the JVM memory to 50m and start iotdb. The memory occupation exceeds 50m
> ----------------------------------------------------------------------------
>
> Key: IOTDB-4013
> URL: https://issues.apache.org/jira/browse/IOTDB-4013
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Server
> Reporter: sunhao
> Priority: Major
> Fix For: 0.13.1
>
> Attachments: image-2022-08-01-20-54-09-083.png,
> image-2022-08-01-20-54-13-180.png, image-2022-08-01-20-54-19-878.png,
> image-2022-08-01-20-54-49-656.png, image-2022-08-01-20-54-57-448.png,
> image-2022-08-01-20-55-23-287.png
>
>
> 1. Set the JVM memory to 50m
> !image-2022-08-01-20-54-09-083.png!
> 2. Restart iotdb and write data with bechmark
> Benchmark configuration:
> !image-2022-08-01-20-54-13-180.png!
> !image-2022-08-01-20-55-23-287.png!
> It can be seen from the above figure that the memory occupation ratio before
> writing data is 1.3, and after writing data, the memory occupation ratio is
> 1.6-1.7
> !image-2022-08-01-20-54-49-656.png!
> The server memory is 7811.2m, so the memory occupied by iotdb is
> {color:#FF0000}132.787m>50m{color}
> {color:#FF0000}unreasonable{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
