{"id":4201,"date":"2017-06-12T05:51:09","date_gmt":"2017-06-12T00:21:09","guid":{"rendered":"\/?p=4201"},"modified":"2020-08-17T11:45:56","modified_gmt":"2020-08-17T06:15:56","slug":"performance-troubleshooting","status":"publish","type":"post","link":"https:\/\/www.argildx.us\/technology\/performance-troubleshooting\/","title":{"rendered":"Optimize Your AEM Website with Performance Troubleshooting Tips"},"content":{"rendered":"
During the initial development phase of a website, not much attention is given to the performance of a website i.e. how the website will respond to millions of requests. Performance means the time your website takes to respond to visitors’ requests. In the later stages of implementation you need to optimize the website to maximize the performance goals. In this article, we will discuss some measures to optimize your AEM website, which is to increase the page load time so as to provide good experience to users.<\/p>\n
Five rules that should be followed to avoid performance issues in AEM sites.<\/p>\n
A project should first be soft-launched to a limited audience in order to gather real-life experience. When the website is live, it is the time when you experience real load on your system.<\/li>\n
After the launch of your website, if there are some performance issues, it means load and performance tests<\/u><\/a> did not simulate reality closely enough. \u201cReal\u201d means real traffic, real content size and real code.<\/li>\n Establishing good performance goals is a tough task. It is often best to collect real life logs and benchmarks from a comparable website.<\/li>\n Only optimize one thing at a time. If you try to do things in parallel without validating the impact of the one optimization, later it will be difficult to figure out which optimization actually helped.<\/li>\n Performance tuning is an iterative process that involves measuring, analysis, optimization and validation until the goal is reached.<\/li>\n<\/ol>\n To optimize your AEM website performance, you need to monitor various attributes of the instance and its behavior.<\/p>\n <\/p>\n 3. Now we will see how many times \u201c\/companyservice\/contact.html text\/html\u201d page is rendered.<\/p>\n <\/p>\n 4. Here we are piping the result into a text file \u2018demo.txt\u2019. Now, we can sort the data by date and get to know what is actually happening on publisher.<\/p>\n 1. Cache ratio<\/strong> means how many requests that come to your system are handled by cache.<\/p>\n 2. Dispatcher Cache Ratio<\/strong><\/p>\n 3. Publisher Cache Ratio<\/strong><\/p>\n 4. Adobe Recommends a Cache Ratio of 90-95%<\/strong> for best performance.<\/p>\n 5. The Dispatcher always requests the document directly from the AEM instance in the following cases:<\/p>\n 6. Calculating Dispatcher Cache Ratio Using Access log and Request log<\/strong><\/p>\n 7. Calculating Publisher Cache Ratio<\/strong><\/p>\n Thus, you can apply some performance enhancing mechanisms to optimize your AEM website like caching the content, measuring page load time before its launch to reduce the response time of your website and thus provide a good user experience.<\/p>\n","protected":false},"excerpt":{"rendered":" During the initial development phase of a website, not much attention is given to the performance of a website i.e. how the website will respond to millions of requests. Performance means the time your website takes to respond to visitors’ requests. In the later stages of implementation you need to optimize the website to maximize … Read more<\/a><\/p>\n","protected":false},"author":29,"featured_media":6661,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","footnotes":""},"categories":[66],"tags":[1794,1796,1795,1409,1408],"yst_prominent_words":[1536,1799,1777,1782,1790,1780,1789,1779,1775,1776,1778,1798,1797,1788,1783,1786,1784,1787,1781,1785],"acf":[],"yoast_head":"\n\u00a0Establish Solid Goals<\/h5>\n
Stay Relevant<\/h5>\n
Agile Iteration Cycles<\/h5>\n
Page Loading Time<\/h5>\n
\n
Performance Guidelines<\/h5>\n
\n
AEM Website Performance Monitoring<\/h5>\n
\n
INTERPRETING THE REQUEST.LOG<\/h5>\n
\n
Basic Commands<\/h5>\n
\n
\n
\nbecause its request is coming to the server again and again.<\/li>\n\n
\n
Calculating Cache Ratio<\/h5>\n
\n
\n
\n
\n
\n