Profiling CQ5... How to profile database access ???

[Peter_Puzanovs]

Essentially, pretty simple task, facing quite large and quite slow CQ5 app. Would love to profile it and see which component takes longest amount of time.

I suspect the problem might live in the number of requests to DB in certain components...

I have already done the <cq:include path=“timing” resourceType=“foundation/components/timing”/> and profiled the app with the Dynatrace.

However, neither of these two show details on the database calls .e.g. accesses to the Jackrabbit.

How do I profile database accesses per component ? What are the options ?

Thanks,

Peter

[Jörg_Hoh · Accepted solution]

Hi,

I would first start with the "Recent requests" tab in the Felix Webconsole. It shows you quite detailled which page and which component in there has which performance (aka takes how much time to render). There you can identify components and start reviewing the individual components. Of course a profiler or a good series of threaddumps are even better, but it's a very good start to identify slow components without administrator's contribution.

Kind regards,
Jörg

[Mshaji]

Have you tried CQ5 builtin profiler? Try these links

http://helpx.adobe.com/experience-manager/kb/AnalyzeUsingBuiltInProfiler.html

http://cq-ops.tumblr.com/post/14171314444/how-to-use-cqs-own-built-in-java-profiler

[Peter_Puzanovs]

Hi,

Yes, I see them both, neither of them show actual calls to the jackrabbit persistence layer...

They just show timings which I already got before.

What are the ways to profile call to the database, e.g. jackrabbit in our case.

Peter

[Lokesh_Shivalingaiah]

I think, existing profile will not hold the details of the call to the database, they more do at the component level.

So You can see if the component which makes the call to your jackrabbit is taking more time, then you can see on the queries you have in that component.

If you need in more detail, I would suggest you to log a ticket with Adobe

[Jörg_Hoh]

Hi,

no, there is no such tool, which show you eclusively the calls to JCR and how long they take. I would recommend to do a few threaddumps and analyze them. We can help you though to analyze it.

kind regards,
Jörg