Expand my Community achievements bar.

Applications for the 2024-2025 Adobe Experience Manager Champion Program are open!
SOLVED

FLUSH AGENT SLOWNESS -PUBLISHER

Avatar

Level 2

During bulk activation , the flush agent queue are getting piled up and slowly moving. Due to this , the latest content is not visible in the site immediately. What are the possible reasons for slowness in flush agent when authoring team doing bulk activation.  The slowness observed recently past 4 month post sp16 upgrade. 

 

1 Accepted Solution

Avatar

Correct answer by
Level 2

Hello @Preetpal_Bindra  and @Shashi_Mulugu  Thank you for your reply. Please be informed we have resolved the issue by upgrading the ACS AEM common package which had flush agent fix in the latest version.

https://adobe-consulting-services.github.io/acs-aem-commons/

View solution in original post

6 Replies

Avatar

Community Advisor

@UdayaKu how much content are you flushing on each page activation? Is it like 1:1 or are you using anything like ACS Cache Flush rules and ACS cache flush UI? Try to reduce number of records getting flushed in each activation also Try to check the dispatcher Throughput as technically it all depends on how performing is your publisher or how fast your dispatcher reacting?

Avatar

Community Advisor

Hello @UdayaKu ,

The replication agents are clearly being overwhelmed however, since you mentioned it started happening only after the upgrade. 2 things to investigate,

1. Compare the number of pages that were published before and after the upgrade.

2. Set logging to debug or trace to observe if there are newer errors that were not there before the upgrade. Splunk or a similar system could help here.

 

thanks,

Preetpal

Avatar

Community Advisor

And,

3. Were there any changes to the AEM architecture, for example number of the AEM publish servers changed, firewall changes, number of apache servers (or similar reverse proxy), or anything else that could have changed before and after upgrade.

4. Is there a performance testing environment that you can use to replicate the scenario with a similar content volume?

 

thanks,

Preetpal

Avatar

Correct answer by
Level 2

Hello @Preetpal_Bindra  and @Shashi_Mulugu  Thank you for your reply. Please be informed we have resolved the issue by upgrading the ACS AEM common package which had flush agent fix in the latest version.

https://adobe-consulting-services.github.io/acs-aem-commons/

Avatar

Community Advisor

@UdayaKu gr8 to hear it got resolved that means you are using some custom feature from ACS as I said above. Nice to know.