I have a huge problem 馃槶
One of our #rustlang micro-service is showing very erratic memory consumption, and our monitoring system is sending alerts because its memory footprint can quadruple in a minute...
It varies between 2 to 8MB 馃槵
(/s , if needed )
i got got - didn't register the mb till i saw comments, so i needed /s :p
@corpsmoderne out of curiosity what framework was that?
@vaguelytagged Axum. To be honest the micro service is mostly idle at the moment, but still.
@corpsmoderne pretty neat. I was wondering if it鈥檚 documented anywhere on the minimum amount of ram needed for Axum itself. Surely it has to allocate in some parts. I know futures are zero allocation.
@vaguelytagged well, about 2 megs :)
To be honest we have another rust/axum MS which use a lot more ram during requests (understandably considering the data it has to handle), and it wasn't giving any of it back with the default allocator. I switched to jemallocator and now it behaves.
@corpsmoderne oh interesting it wasn鈥檛 giving it back? Did you ever figure out why? Was it just the way it was fragmented? I used to have Axum as a static file server for my blog but it oomed when it hit front page and I never really root caused it. My understanding was that it shouldn鈥檛 really have to allocate to handle simple requests but then again I haven鈥檛 really looked at the source code for Axum
@vaguelytagged yeah never proved any of it but I believe we allocated a lot of very fragmented bits of memory. Jemallocator was the lazy fix but it solved it for good. It's clear we have huge performance gains to make by improving our memory allocation though, but don't need it for now.
@corpsmoderne Is there some huge loop that is teasing the compiler into thinking that the variables all need to hang around for ages before the function/method finishes, so that a whole bunch of stuff gets held in stack/heap until the loop exits?
If the loop is allocating a lot of stuff while it does its thing, then maybe you'd enter the loop with only a couple of megabytes in use, and not exit the loop until you had eight megabytes in use.
@bobulous dude, that micro service is fine ^^
@corpsmoderne Oh, I've just understood the sarcasm.
I thought maybe this was in an embedded system where eight megabytes was pretty much the entire available RAM.
@corpsmoderne 馃 My smartwatch has more RAM...
