I'm Anton, and I wanted to show you this tool that I have been building over the last year or so. It's based on experience from working with performance of Java apps (particularly Elasticsearch), and would have made my life so much easier in that role.
I would love feedback on essentially everything! You can see the core of the product by pressing the "demo" button on the top of the landing page. Thanks in advance :)
1) What is the performance impact under typical production loads? Many JVM profilers are absolutely brutal to JVM performance and can't be realistically used in Production.
2) How does this compare to the lightweight JVM profilers offered by New Relic and Dynatrace?
1) The agent is based on the Java Flight Recorder (https://en.m.wikipedia.org/wiki/JDK_Flight_Recorder) which is a technology built into the (Oracle/OpenJDK) JVM. The performance impact is thus rather small, around 1-2% of CPU.
2) To the best of my knowledge, New Relic and Dynatrace can't provide similar levels of JVM metrics (e.g. which methods allocate the most memory), since they are based on JMX metrics rather than flight recorder data. They do however have better APM functionality and framework integration than Blunders.
Comments
Hi HN!
I'm Anton, and I wanted to show you this tool that I have been building over the last year or so. It's based on experience from working with performance of Java apps (particularly Elasticsearch), and would have made my life so much easier in that role.
I would love feedback on essentially everything! You can see the core of the product by pressing the "demo" button on the top of the landing page. Thanks in advance :)
Anton, looks cool. A couple questions if I may:
1) What is the performance impact under typical production loads? Many JVM profilers are absolutely brutal to JVM performance and can't be realistically used in Production.
2) How does this compare to the lightweight JVM profilers offered by New Relic and Dynatrace?
Thanks!
Thanks for checking it out!
1) The agent is based on the Java Flight Recorder (https://en.m.wikipedia.org/wiki/JDK_Flight_Recorder) which is a technology built into the (Oracle/OpenJDK) JVM. The performance impact is thus rather small, around 1-2% of CPU.
2) To the best of my knowledge, New Relic and Dynatrace can't provide similar levels of JVM metrics (e.g. which methods allocate the most memory), since they are based on JMX metrics rather than flight recorder data. They do however have better APM functionality and framework integration than Blunders.
A note: the "Memory allocation flame chart" image isn't rendering for me in Firefox. It renders in Chrome.
Thanks for noticing, I have been noticing the same thing. Trying to figure out why, usually it works just fine in FF as well.