cichengzi opened a new issue, #3059: URL: https://github.com/apache/hugegraph/issues/3059
### Problem Type (问题类型) None ### Before submit - [x] 我已经确认现有的 [Issues](https://github.com/apache/hugegraph/issues) 与 [FAQ](https://hugegraph.apache.org/docs/guides/faq/) 中没有相同 / 重复问题 (I have confirmed and searched that there are no similar problems in the historical issue and documents) ### Environment (环境信息) - Server Version: 1.5.0 (Apache Release Version) - Backend: RocksDB - OS: 4 CPUs, 32 G RAM, Ubuntu 22.0 - Data Size: 450w+ vertices, 1000w+ edges ### Your Question (问题描述) I'd like to know how HugeGraph 1.5.0 handles memory reclamation and control in RocksDB storage mode. After repeatedly creating graphs, adding nodes and edges, and performing Gremlin queries, memory usage remains consistently high. What can I do to get that memory reclaimed and released? Even after I executed a Gremlin query task with a large amount of data, all the HugeGraph backend interfaces became unusable. No matter which interface I called, it would eventually result in an InterruptedException or Timeout. ### Vertex/Edge example (问题点 / 边数据举例) ```javascript ``` ### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构) ```javascript ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
