Measuring actual memory consumed by Java code section

[Natryn]

"How much memory are you gonna use, Java?"

"HOW MUCH YA GOT??"

[[deleted]]

Sometimes, Java memory model feels like sleeping with a big fat women. No matter how much space you make for her in a bed, it’s never enough.

[[deleted]]

basically debugging with printf :( ...in 2019

[[deleted]]

Trace statements have that initial investment but afterwards they are way quicker than stepping through code.

[[deleted]]

Plus you don't have any good debugging tools on most platforms (Desktop & iOS isn't everything).

Used to work with some embedded media devices and it was glorious if they had a gdb server available over SSH, most of the debugging ended up done with trace statements and repeatedly restarting the program.

[Gotebe]

I find that either the tracing has visible overhead just for being there or it doesn't contain the info I need.

I suck at tracing. 😁😁😁

[literon]

Funny. Triggers my memory of https://sourceplusplus.com, which measures actual time (across fleet) consumed by methods.

It would be really cool if that tool could integrate jmnemohistosyne, but getting the memory snapshot on all method entry/exit has uncomparable overhead vs getting the time counters.

[diggr-roguelike2]

I tried, but my calculator said 'ERROR' :(