Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

JPorifler, YourKit, etc.

Avatar

Level 7

I am looking for a powerful profiler that can be configured for our CQ installation, on all our environments from dev to prod.

Something with minimal performance impact that can be connected to remotely too.

Any suggestions in this regards?

Thanks in advance.

1 Accepted Solution

Avatar

Correct answer by
Level 6

Hi,

first of all, you should not run a profiler on a production environment if you don't have problems that only occure in production. However, you should use a JMX Monitor to log memory usage and such and if you find yourself in trouble that you can't solve in another environment, then push the profiler to the environment. Don't monitor unless you need to.

Over the years, I have taken a like in YourKit. It seems to be the one that has the least impact on the system. Some years ago, we got the error when we run a production system but not when using a profiler. Root cause was a timing problem and any other profiler than YourKit was to intrusive.

To enable a profiler, all you need to do is point to the agent. You can find one solution at http://cq-ops.tumblr.com/post/14129727991/how-to-enable-yourkit-java-profiling-in-cq-on-windows and http://helpx.adobe.com/experience-manager/kb/HowToConfigureYourKitJavaProfiler.html.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 6

Hi,

first of all, you should not run a profiler on a production environment if you don't have problems that only occure in production. However, you should use a JMX Monitor to log memory usage and such and if you find yourself in trouble that you can't solve in another environment, then push the profiler to the environment. Don't monitor unless you need to.

Over the years, I have taken a like in YourKit. It seems to be the one that has the least impact on the system. Some years ago, we got the error when we run a production system but not when using a profiler. Root cause was a timing problem and any other profiler than YourKit was to intrusive.

To enable a profiler, all you need to do is point to the agent. You can find one solution at http://cq-ops.tumblr.com/post/14129727991/how-to-enable-yourkit-java-profiling-in-cq-on-windows and http://helpx.adobe.com/experience-manager/kb/HowToConfigureYourKitJavaProfiler.html.