You can use AEM Developer Mode [1] to know the timing of each component.     [1] https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developer-tools/developer-mode.html

@Rohan_Garg Usually browser/search engines make favicon request under root domain, ie. /favicon.ico   I suggest you add a redirect rule to handle this request   RewriteRule ^/favicon.ico$/etc.clientlibs/brandA/clientlibs/clientlib-favicon/resources/favicon-brandA-32x32.png [PT,NC,L]   * Just test if...

You can follow the steps mentioned in this guide [1]   [1] https://experienceleague.adobe.com/docs/experience-manager-65/administering/integration/experience-fragments-target.html?lang=en

I agree with @arunpatidar , 700 req/sec is a sign of attack. DDoS should be able to handle it.   If you have applied all best practices and looking for better throughput, you have to consider scaling options.

@Ian_2021 Scanning logs is my personal recommendation based on capacity. I find it helpful to improve the health of the server.   Where did you find about publisher throughput of 700 req/sec ? Is it documented in Adobe documentation?  Please note that you can do vertical/horizontal scaling to increa...

Understood. I recommend the following in such a scenario: Make sure to apply recommended best practices to the publisher [1] [2] [3]Configure DDoS Protection [4] on CDN, this will block any attempt of attack on the server.Continuously scan your publisher logs, to find common 404 patterns and add the...

Give it a try on fresh instance, if you are facing same issue, please reach out to Adobe support team.

This is a strange scenario where you are trying to measure the performance of the server by putting a load of 404 requests. In such case, the dispatcher/CDN cache can not be leveraged and requests will always reach to the publisher.   Ideally, in the case of 404, the publisher should do only resourc...

Girish, have you tried replicating this issue on a fresh AEM instance with the demo site?

I am using AEM (6.5.10 and above / AEM Cloud SDK) on mac with m1 chip without any issue. So from a backend point of view, it should be seamless with the latest AEM JAR. See this thread for same topic [1]    You may need a special version of the dispatcher to support m1 chip, see this discussion for ...