Hi folks, I work with Samiksha on the above-mentioned system.
A little more context (in case it's relevant);
Our sites are hosted by Adobe Managed Services on regular AWS infrastructure.
We are on the basic (lowest) AMS tier.
So I just selected one of our pages through the /sites.html/ interface while logged in with a regular editor account. That initial request timed out with a 504 gateway error. (I suspect that this error is specifically occurring at the Dispatcher/ELB level as we have to directly access the Author server by IP address and port number in order to upload large packages without hitting similar timeouts. I forget whether we determined that that timeout was happening at the ELB or the Dispatcher)

The raw response headers were simply
HTTP/1.1 504 GATEWAY_TIMEOUT
Content-Length: 0
Connection: keep-alive
The user interface on page displayed "An error occurred while refreshing list of references." in the left hand references pane.
So that first request looks to me like it just got timed out after 1 minute (59149 ms)
Retrying the request for the same page by IP address succeeds, though still takes roughly 60 seconds.
Retrying the request for the same page by IP as the admin AEM account on that server succeeds and takes roughly 30 seconds.
The response document that AEM sends to the request from the Admin account contains what appear to be debug comments ( e.g.
<!--cq{"decorated":false,"type":"wcm/msm/components/coral/references/livecopy","path":"/content/bmc/gr/en/redirects/it-solutions/remedyforce-features-integrations","selectors":null,"servlet":"Script /libs/wcm/msm/components/coral/references/livecopy/livecopy.jsp","totalTime":5,"selfTime":5}--> ) but is otherwise identical. As in bitwise identical once the lines containing comments are stripped.
The response document (which appears to contain just regular HTML) is 600 lines long and just under 50K in size.
I'm assuming that the admin request is consistently processed faster (~X2) because the server does not need to do as many layers of security checking, but that's just a guess.
Sometimes reference checks take in excess of 3 minutes to complete, generally for content with more history. However, none of the content in our system is more than 9-ish months old, we haven't had revision generation on publish turned on. The times taken seem excessive.
Thoughts?