How to find AEM component load time in a page

Statement - How to find AEM component load time in a page

Pre-requisite :

  • AEM 6.3 server up and running
  • JRE 1.8

Solution :


  • Go to the any page of the site for example http://localhost:/editor.html/content/we-retail/us/en/experience.html
  • On page switch to developer view 
  • On same page click on toggle side panel --> click on the component.
  • Now select any one of the component,As per this example selecting ArtcleList component shown in Screenshot.

  • In the left side panel Article list component shows the total load time for this component is 0.017 ms
  • Now if you want see the details of this component click on the copy icon under the Articlelist component which 
                       - Shows list of scripts included for this component.
                       - Content Path for this component.
                       - On click on each of the script file takes you to the CRX/de light console


    • Click on pencil icon will take you to the Articlelist component script in crx/de light console and you can tune the application code if response time is low.

    • Below screenshot shows the load time in millisecond for different components used in the experience.html page

1 comment:

AEM 6.0 New Features


Statement - AEM 6.0 new features

Features-
1.       Jackrabit 3(Oak) is used for repository re-write persistence.
§  Persistence Manager(PM)is out.
§  Uses Micro Kernels such as
o   SegmentMK – TarMK
o   DocumentMK – MongoMK
§  MVCC – Multi version concurrency control
§  Garbage collection(revision cleanup) on daily basis to avoid the repository/disk volume grow.
§  Oak run tool – for offline compaction – Server down time is required.
2.       Tar files are now memory mapped(off heap) , whereas for in older version in-heap CRX bundle cache concept has gone.
3.       Oak- All content are not indexed automatically, if at all required for efficient searches ,need to create/add manual indexes.
4.       Sling Health check monitoring tools.
5.       CQSE servlet engine is replaced with Eclipse Jetty.
6.       In Scene7 Image server – for creating dynamic image renditions on demand rather than prebuilt static image renditions.
7.       Clustering
1.       No more Active-Active CRX(Tar MK) Clustering
2.       TarMK cold standy active-passive clustering for availability but not for scaling
8.       New MongoDB based Active-Active(MongoMK) clustering
9.       New logback logging framework – for the configuration of external logging XML will be used
10.   ExtJS based sidekick has been deprecated, html5,CSS and JQuery used in new sidekick
11.   Binaries can be store on different disk volume (file Data Store), Data can be stored in S# data store AEM instance can be deployed on premise, cloud and non-cloud.
12.   Irrespective of data store (node store, data store..etc) all the binaries are stored and saved as *.tar  files in /crx-quickstart/segmentstore/ , lucene indexes also stored in the nodestore.
13.   Below console are renamed
§  Web content management(WCM) console to à Sites
§  Digital asset management(DAM) console to  à Assets
§  SoCo –Social communities to à Communities


No comments:

Apache Felix Jetty Based Http Service configuration file Location in AEM 6.3

Statement : 
                 In a cluster environment by mistake if  you change port number apart from the one on which the instances are running  in the Apache Felix Jetty Based Http Service

Pre-requisite :
                 -  AEM servers runing on port : 8080
                 - Changing the port of any one of server in cluster to 4502.

Risk Mitigation :
  • Edit the properties of Apache Felix Jetty Based Http Service file in the below path  for each server
                             \crx-quickstart\launchpad\config\org\apache\felix\http

  • Jetty file location path:


  • Edit the configuration file to revert back to the original port number



  • Re-start the AEM instances one by one.
  • Thats's it!.

No comments:
Subscribe to: Posts (Atom)