Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

Akamai cache clear

Avatar

Level 3

Hi AdobeCommunity Family,

In our every release process, we're encountering manual overhead when clearing the Akamai cache. This leads to high CPU usage and sluggish performance on our publishing servers.

Can you please provide guidance on automatically clearing the cache and replicating the code across publishers without the need for manual CP code addition in akamai.

 

Thanks

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Sai1278 
We are using CDN and following rules?

1. CS/JS/Images are cached for long 30 days

2. Pages are cached for 30 min

3. Config jsons are cached for 30 min/ no cache CDN for eager loader

 

we are using hashed CS/JS, so whenever the CSS and JS changed, we get the new references. So does the images.

However we are clearing entire CDN cached during deployment. We have monthly deployment cycle. But this does not impact us, because we are using Blue/green deployment, which allow us to test releases in Blue environment before we enable for Live, testing in Blue environment does warmup the dispatcher cache, which reduce the load on publishers during go live.

But CDN cache should be based on TTL, which should not be explicitly cleared until releasing the new code.



Arun Patidar

View solution in original post

4 Replies

Avatar

Community Advisor

@Sai1278 the ideal state of CDN setup is to go with TTL based Cache settings , such that pages will be cached for minimum time and clientlibs,  images are cached for maximum ttl .. so that there should not be any need for cache flush..

Avatar

Level 3

Hi @Shashi_Mulugu @EstebanBustamante  

After every release the CSS and JS are not reflecting on the pages. Only after clearing the Akamai cache can we see the changes. In these scenario is there any way to automatically relicated changes in publish env through replication agent?

Avatar

Correct answer by
Community Advisor

Hi @Sai1278 
We are using CDN and following rules?

1. CS/JS/Images are cached for long 30 days

2. Pages are cached for 30 min

3. Config jsons are cached for 30 min/ no cache CDN for eager loader

 

we are using hashed CS/JS, so whenever the CSS and JS changed, we get the new references. So does the images.

However we are clearing entire CDN cached during deployment. We have monthly deployment cycle. But this does not impact us, because we are using Blue/green deployment, which allow us to test releases in Blue environment before we enable for Live, testing in Blue environment does warmup the dispatcher cache, which reduce the load on publishers during go live.

But CDN cache should be based on TTL, which should not be explicitly cleared until releasing the new code.



Arun Patidar

Avatar

Community Advisor

Hi,

 

This is a good article to read: https://cqdump.joerghoh.de/2024/06/12/my-view-on-manual-cache-flushing/ that can help evaluate why this could be happening. Other than that, i agree with @Shashi_Mulugu , TTL based should be the way to go

 

Hope this helps



Esteban Bustamante