AEM Performance Issue for Popular Pages | Community
Skip to main content
S
S__k__Agarwal
Level 3
April 27, 2025
Solved

AEM Performance Issue for Popular Pages

  • April 27, 2025
  • 1 reply
  • 401 views

A news portal AEM client is complaining of performance issues on their site. The site has a particular traffic access pattern where about 90% of the traffic is concentrated on a small fraction of the following content pages.

 

• The Home Page
• Campaign Landing Pages
• Featured News Pages

 

Which approach should the Architect take to avoid any future performance issues?

 

❑ Implement a Re-fetching Flush Agent
❑ Implement cache flushing from Author
❑ Add “.jpg” and “.png” to the auto-invalidation configuration in the dispatcher
❑ Implement cache flushing from Publish

 

@aanchal-sikka @EstebanBustamante 

@arunpatidar @Shashi_Mulugu 

@lukasz-m @Mahedi_Sabuj 

@kautuk_sahni @Sudheer_Sundalam

@lukasz-m @Rohan_Garg 

 

Best answer by ShivamKumar

Hi @s__k__agarwal ,

 

I think option 4 is correct. By implementing cache flushing from Publish, the dispatcher can invalidate cached content only when the content is published and live. This ensures that users see the most up-to-date version of the website without clearing cache unnecessarily early. It also maintains the cache for critical high-traffic pages like the homepage and featured news until necessary, improving overall performance.

Option 1 (Implement a Re-fetching Flush Agent) can also be correct because it refreshes only the updated content in the cache without requiring a full cache flush. This helps keep the cache fresh while minimizing the performance impact, which is very useful in a high-traffic environment.

Thanks.

1 reply

S
ShivamKumarAccepted solution
Level 4
April 27, 2025

Hi @s__k__agarwal ,

 

I think option 4 is correct. By implementing cache flushing from Publish, the dispatcher can invalidate cached content only when the content is published and live. This ensures that users see the most up-to-date version of the website without clearing cache unnecessarily early. It also maintains the cache for critical high-traffic pages like the homepage and featured news until necessary, improving overall performance.

Option 1 (Implement a Re-fetching Flush Agent) can also be correct because it refreshes only the updated content in the cache without requiring a full cache flush. This helps keep the cache fresh while minimizing the performance impact, which is very useful in a high-traffic environment.

Thanks.

Terms & ConditionsAccessibility statement

Loading footer...