GitLab

I wonder how we can better track down the extremely high memory usage on some dirauths. For gabelmoo, I notice that the usage is certainly a lot higher than it used to be, and that it seems to grow rapidly with drawn-out multiple day "plateau" phases of virtually no increase in memory footprint. What are debug mechanisms (beyond our default usage of valgrind, which doesn't think there are any leaks) that I might be able to use here?

This is a somewhat big issue for me, as gabelmoo makes the system swap and therefore unresponsive, so that I have to restart it frequently