CQ Performance difference | Community
Skip to main content
Level 4
October 16, 2015
Solved

CQ Performance difference

  • October 16, 2015
  • 2 replies
  • 747 views

Hi,

We feel that the CQ's performance on a server and on a desktop is very different.  Both machines have the same Java version, yet with the same content, loading time on the desktop is very much faster than the server.  The server's memory and CPU power are more superior than the desktop's, so it is very frustrating to find that the server is performing more slowly than a desktop.

A page that takes 70ms to load on a desktop (per the request log), takes 7000ms to load on the server.  What should we check and do to find out why the server is behaving this way?

Thank You.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

First check that the hardware is indeed superior. (I had that experience too and it turned out the the super-duper-server had 32 cores, but only with 1Ghz each (Sun T1), while the desktop was a core2duo with 2.5 ghz).

Then check the system monitoring of the server. Is the system CPU or I/O-bound? Then analyze the request using http://host:4502/system/console/requests where you can see how long each component took, using that you should be able to identify the hot spots.

2 replies

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

First check that the hardware is indeed superior. (I had that experience too and it turned out the the super-duper-server had 32 cores, but only with 1Ghz each (Sun T1), while the desktop was a core2duo with 2.5 ghz).

Then check the system monitoring of the server. Is the system CPU or I/O-bound? Then analyze the request using http://host:4502/system/console/requests where you can see how long each component took, using that you should be able to identify the hot spots.

Level 4
October 16, 2015

Hi,

The issue was with the replication setup in our instances.  Replication was incorrectly set, causing loops, which dragged down performance.  After correcting this, performance is back to normal (comparable to a local machine hosted CQ)

Thank You.