AEM page load time

In the process of debugging performance issues, we need to narrow down the load time of the page and hence the individual component/requests part of the page.
Below are the few ways of finding out the same. 

  • From Browser : The very first place where we look for the page load time is our browser's Developer tools->Network Tab which will display the time taken for each of the requests that are part of the page.
  • AEM Component load time: We have an OOB feature on the AEM Sites page to find out the load time of a component. 
    • Open AEM Site Page in editor mode(with /editor.html) -> Switch to Developer mode from Edit mode -> Left rail in content finder area -> Components section -> Components available as part of the page will be displayed with the time taken.
  • request.log: 
    • request.log file available in ../crx-quickstart/logs folder will have a trace of each and every request and its duration. 
    • There exist a Request Log Analyzer available OOB in ../crx-quickstart/opt/helpers/rlog.jar which will help find out the requests which took a longer duration to respond.
      • clear out existing contents in request.log file -> Access an AEM page -> logs would have been trapped in request.log file. 
      • Let's say we have to display 5 requests in the order starting with longest duration, execute the below command being in /crx-quickstart/logs folder of AEM instance. 
        • java -jar ../opt/helpers/rlog.jar -n 5 request.log where n refers to the number of lines to be displayed
  • AEM Chrome plugin from ACS Commons:
    • Log tracer and Adaptive form are the primary functionalities, covered in detail in ACS site
    • To find out load time of the request: Chrome browser  -> Developer Tools -> AEM Tab -> Tracer -> Will have a list of requests of the page with time displayed under "Response time" (After installing the plugin by following installation steps in ACS site)

Comments

Post a Comment

Popular posts from this blog

Embedding Third party dependency/OSGi bundle in AEM application hosted in AEMasCS

Image
This post illustrate the ways of embedding third party dependency in AEM maven project. Steps are mentioned considering the project structure to be followed for AEMasCS while the same can be followed for classic versions too.  Before we begin, I would like to explain the scenario of including a dependency in our AEM maven project.  When we would like to make use of an API that is not already available in our project, we look for that in maven-central repository and specify the dependency in main pom.xml and desired module's pom.xml file. (Lets say, AWS S3 Java SDK V2 dependency) Upon updating the project in the IDE, we would see our class files (making use of those APIs) are compiled/build successfully without any errors.  Now, in the context of AEM/OSGi environment, when the same package and hence the bundle is deployed to AEM instance, dependencies that we added new might not be resolved/available in the OSGi as a bundle. Something like the below This indicates that the...
Read more

OSGI Factory Configuration implementation

OSGI Factory configuration is used to have many instances of an OSGI config (represented/identified via an identifier) for the single OSGI service/PID. Most often used OOB Factory configurations for example: Logger Factory/writer configuration (for log statements) Service user Mapper service Amendment (for using service resource resolver in projects) Few sample real time use case for the need of OSGI factory config: For multi tenant projects, if we have generic service used across tenants with properties/attributes specific to tenant. For single tenant, generic service targeting all locales with properties/attributes specific to locale. (where generic service -> holds logic in the lines of calling third party service for retrieving/updating information.) Implementation: ( In terms of OSGI R6 annotations ): Create Object Class Definition(OCD) defining desired properties for the OSGI service. - OSGIFactoryConfigOCD.java OSGI Service/Factory service to retrieve ...
Read more

Embed Third party dependency using bnd-maven-plugin

Image
This post explains the use of bnd-maven-plugin to embed third party dependency  Two main instructions of bnd-maven-plugin that serves the purpose are detailed below.  -conditionalpackage  pick packages from respective library and copy them in the bundle. Any dependencies of those copied packages will also be copied if they match the selectors. This means we need to explicitly list all the Java package names of desired dependency as part of this instruction (including its transitive dependencies) More about conditionalpackage instruction from official docs -  https://bnd.bndtools.org/instructions/conditionalpackage.html -includeresource  For including resource inline -includeresource: @artifactId-version.jar!/* For embedding as a jar with an entry in bundle class path -includeresource: artifactId-version.jar;lib:=true For several other possible combinations for including the resource, please check - https://bnd.bndtools.org/instructions/includeresource.html Wi...
Read more