Now if we only had one for memory usage that recursively broke it down by types from top level containers! That would make tracking production memory hogs easier!
Oh my god you don’t know how much this means to me. I’ve been trying to track down memory issues for months due to heavy objects from the database and a possible leak - this is exactly what I was looking for to put into use! I can now have a periodic dump suitable for stdout scraping. Thank you!
Great! Let me know how it goes (I am working on making the malloc-tracking functionality even faster, too).
One thing: relying on the ASCII art output is going to be pretty brittle. It wouldn’t be hard to have this info be generated in CSV or JSON format (I’d prefer the latter). If that sounds helpful, please don’t hesitate to open an issue!
Ooh ooh!!! I can totally plug this in!
Now if we only had one for memory usage that recursively broke it down by types from top level containers! That would make tracking production memory hogs easier!
Not sure if breaking down by types is necessarily that helpful, but Scalene not breaks down CPU and memory usage on a per-line basis.
Oh my god you don’t know how much this means to me. I’ve been trying to track down memory issues for months due to heavy objects from the database and a possible leak - this is exactly what I was looking for to put into use! I can now have a periodic dump suitable for stdout scraping. Thank you!
Great! Let me know how it goes (I am working on making the malloc-tracking functionality even faster, too).
One thing: relying on the ASCII art output is going to be pretty brittle. It wouldn’t be hard to have this info be generated in CSV or JSON format (I’d prefer the latter). If that sounds helpful, please don’t hesitate to open an issue!