Fully featured low overhead profiler for Java EE and Java SE platforms.
Ultimate profiling and monitoring solution for Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

Exception telemetry is not terribly useful

Moderators: Vladimir Kondratyev, Anton Katilin

Exception telemetry is not terribly useful

Postby james.leatherman » Wed Jun 18, 2014 12:01 am

1.) No line numbers
2.) Too many steps to export full stack text
3.) No drilldown capability
4.) No context in live or snapshot mode

Really, the fist item is the most important to me. Are you planning on changes in exception telemetry?
james.leatherman
 
Posts: 12
Joined: Tue Jun 17, 2014 11:49 pm

Re: Exception telemetry is not terribly useful

Postby Anton Katilin » Wed Jun 18, 2014 7:46 am

Hello James,

1.) No line numbers

Exception telemetry does not offer line numbers for performance considerations.
The profiler must maintain a balance between result verbosity and profiling overhead.
Exception telemetry provides an overview of possible sources of excessive exception activity, which can be a performance issue, and a per-method result granularity is in most cases enough to easily locate the problems.

Anyway, I've added a feature request to provide an option to record line numbers too.

2.) Too many steps to export full stack text
3.) No drilldown capability
4.) No context in live or snapshot mode

Could you please explain each item in more detail. How would you like this information be presented instead?

#2: Do you want a list of all stack traces, e.g. sorted by invocation count?

Anyway, if you need more detail about thrown exceptions, please consider alternate approach: trigger on method invocation:
http://www.yourkit.com/docs/java/help/triggers.jsp
For example, you can use a trigger on method invocation, with the exception class constructor being the target,and print/record method actions.

Best regards,
Anton
Anton Katilin
 
Posts: 5575
Joined: Wed Aug 11, 2004 8:37 am

Re: Exception telemetry is not terribly useful

Postby james.leatherman » Mon Jun 30, 2014 4:01 pm

Hi Anton -

Thanks for the quick reply - that means a lot when choosing to work with a tool vendor. And I appreciate the enhancement request for the option to include line numbers in the exception stack. It really does make a big difference.

Bear in mind that I have been using HP Diagnostics for many years, and the feature set is my benchmark for evaluating other profilers. HP does a great job of creating context by allowing you to drill down from server calls to methods to SQL to cross-VM... you get the idea. Also HP Diags are highly configurable to reduce overhead. Although I value your approach of ensuring low impact out of the box, I also would like a little bit of rope to hang myself if I want to. :)

And yes, I will start working with Triggers to see if I can get what I need that way. Thanks!
james.leatherman
 
Posts: 12
Joined: Tue Jun 17, 2014 11:49 pm

Re: Exception telemetry is not terribly useful

Postby Anton Katilin » Tue Jul 01, 2014 10:48 am

Hello James,

We'll add line numbers in some profiling results in the next EAP build.

Did you have a chance to try the triggers?

Best regards,
Anton
Anton Katilin
 
Posts: 5575
Joined: Wed Aug 11, 2004 8:37 am

Re: Exception telemetry is not terribly useful

Postby james.leatherman » Wed Jul 02, 2014 4:37 pm

Unfortunately, our exceptions are a bit out of control right now, so triggers are not the best method for me.

I have 68 installed, but I don't see the line numbers. Do I need to enable some other collection?
james.leatherman
 
Posts: 12
Joined: Tue Jun 17, 2014 11:49 pm

Re: Exception telemetry is not terribly useful

Postby Anton Katilin » Wed Jul 02, 2014 5:22 pm

Hello James,

Build 14068 is the first one offering line numbers, and they are not available in all profiling modes yet. In particular, they are still missing in exception telemetry. We'll cover exceptions soon, in one of upcoming builds. I'll notify when it's ready.

Best regards,
Anton
Anton Katilin
 
Posts: 5575
Joined: Wed Aug 11, 2004 8:37 am

Re: Exception telemetry is not terribly useful

Postby james.leatherman » Wed Jul 02, 2014 7:17 pm

OK - cool. Thanks for the heads up, and thanks again for the functionality.
james.leatherman
 
Posts: 12
Joined: Tue Jun 17, 2014 11:49 pm

Re: Exception telemetry is not terribly useful

Postby Anton Katilin » Mon Jul 07, 2014 3:09 pm

Hello James,

FYI: build 14072 shows exception telemetry with line numbers:
http://www.yourkit.com/eap

Best regards,
Anton
Anton Katilin
 
Posts: 5575
Joined: Wed Aug 11, 2004 8:37 am

Re: Exception telemetry is not terribly useful

Postby james.leatherman » Wed Jul 22, 2015 5:56 pm

Thanks!
james.leatherman
 
Posts: 12
Joined: Tue Jun 17, 2014 11:49 pm


Return to Java Profiler

Who is online

Users browsing this forum: Bing [Bot], Yahoo [Bot] and 13 guests