What can I do to keep the memory low and log files occupied less space without restarting Rocksdb

With rocksdb, after running for a short time, the memory occupied by the application will change from 1G to 20G, and the log file will occupy 30G. After the application restarts, the initialization of rocksdb will take a long time, such as 10 minutes. The rocksdb log will be reduced from 30G to 300M, and the rocksdb memory will also be reduced a lot, which can be 1G.

What can I do to keep the memory low and log files occupied less space without restarting Rocksdb?

First compare the reported memory and log growth with RocksDB's documented behavior, then reproduce it using the described workload. No source file, test, or entry point is named; done would require a narrowed, reproducible failure and a specific code or documentation change.

Written by the indexing model from the issue text.