TLAB events create misleading flame graphs

Using -e allocation-tlab seems to count the allocation events instead of counting the amount of memory allocated at that stack frame. This means that the flamegraph will show stacks that allocate often, even if they only allocate a few bytes.

As a user I’d expect the flamegraph to point me to the stacks that actually consumed the most memory.

[oehme]

You can take a look at my fork, it contains a couple of improvements:

• tlab allocations now measure the tlabSize, the size is converted to kB
• io and blocking are now measured by their duration instead of their count
• the code for labeling and unit conversion is now in the EventType enum
• the project is now built with Gradle so that there is a 1-step install process
• broken stack frames no longer crash the tool

[chrishantha]

I checked your fork and saw all your improvements. (I actually saw your fork before your comment). Would you like to send a PR to my project?