I believe that the issue here arises from design incompatibilities between the complex engineering code and ptmalloc.
Modifying malloc parameters through mallopt is not user-friendly for database users and can be overly complex.
Moreover, setting certain parameters may lead to performance issues.
Monitoring memory usage should be a common practice for all database users.
With my signal-based approach, we can trigger a trim operation
when high memory usage is detected or by setting up a scheduled task.
This reduces the complexity for users and also helps in lowering memory consumption.
Of course, this solution is not perfect and does not address the problem elegantly from a fundamental perspective.
However, it has proven effective in the user environment.
I have set up a scheduled task to execute a function every 10 minutes for processes exceeding 50MB.
This has reduced memory usage from 87% to 30% on a 64GB system.
