I’m experiencing significant memory usage issues with Influxd.exe on a Windows environment and could use some guidance. Here are the details:
Problem
The Influxd.exe process is consuming over 120GB of memory on our Windows server, leading to performance concerns. This problem has occurred multiple times, and we’ve implemented various steps to mitigate it.
Steps Taken So Far
-
Memory Limitation Testing: We attempted to limit memory usage, but on Windows, InfluxDB doesn’t seem to support this as it does on Linux.
-
Detailed Logging: We enabled detailed logging to track the memory spike events, although it requires an InfluxDB restart to fully take effect.
-
Threshold Monitoring: SMS alerts are set to notify us when memory usage reaches 40% and 50%.Configuration Details
We’ve configured the InfluxDB instance according to our customer’s provided configuration. Despite this, we’re unable to prevent the high memory usage, likely due to the limitations in Windows environment memory control.
Questions
-
Are there any known optimizations or workarounds within the InfluxDB configuration that might help reduce memory usage in a Windows environment?
-
Would adjusting cache or WAL file settings be effective in controlling memory usage?
-
Is there any recommended approach for managing memory usage on Windows without switching to a Linux environment?