Open stokito opened 6 years ago
Nice, thanks for the pointer. Clearly, everyone should switch to JOL, which would certainly receive better maintenance than this library. Memory measurer exists only because something like jol didn't exist some 10 years ago.
Thanks, Dimitri
On Sun, Aug 12, 2018, 10:39 PM Sergey Ponomarev notifications@github.com wrote:
OpenJDK now provides a tool Java Object Layout http://openjdk.java.net/projects/code-tools/jol/ which gives precise numbers for HotSpot. Is any advantage of the memory-measure against JOL? I mean anything what it can do that JOL don't? Is nay reason why you support the library instead of merging it into JOL?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/msteindorfer/memory-measurer/issues/2, or mute the thread https://github.com/notifications/unsubscribe-auth/AJCpPJ0_rc3LRLhKA4LTvAfZaLt3Tt-xks5uQISIgaJpZM4V5qSg .
Hi @DimitrisAndreou Thank you for an answer. Then maybe it worth to mention about JOl somewhere because the memory-measurer was mentioned in few articles in web and in conference talk.
OpenJDK now provides a tool Java Object Layout which gives precise numbers for HotSpot. Is any advantage of the memory-measure against JOL? I mean anything what it can do that JOL don't? Is nay reason why you support the library instead of merging it into JOL?