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.

Is network a polluting factor when doing remote profiling

Moderators: Vladimir Kondratyev, Anton Katilin

Is network a polluting factor when doing remote profiling

Postby bungrudi » Fri Dec 08, 2017 5:39 am

When doing remote profiling, will network latency between the app/agent and yourkit desktop affect app under test's performance?

Will it be better to capture profiling data from the application server using command line yjp-controller-api-redist.jar ?
bungrudi
 
Posts: 10
Joined: Thu Aug 13, 2015 2:49 am

Re: Is network a polluting factor when doing remote profilin

Postby Anton Katilin » Fri Dec 08, 2017 7:46 am

Hi,

Remote profiling data transfer is performed in a dedicated profiler agent thread, so normally the transfer should not make any noticeable effect on profiled application's performance.

Capturing profiling data from the application server using command line yjp-controller-api-redist.jar will have even smaller effect, so you may of course use this approach instead of remote profiling if necessary.

But again, in most cases remote profiling is not a problem for performance, and should be preferred as the easiest way of profiling. So I suggest to start using it, and switch to command line for performance reasons only if necessary for your particular application.

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


Return to Java Profiler

Who is online

Users browsing this forum: No registered users and 23 guests