Content Replication performance from author to publish instance

[mohanb]

Hi All

Am replicating content from author to publish instance, for about 500MB of DAM content it's taking around 3hours when i perform activate tree. PDF, Images and other DAM assets go replicates to publish instance faster. But content fragment replication is relatively slower and taking lot of time. Do we have to make any fine-tuning to improve the publishing performance, please let know.

[mohanb]

Is this a way to expedite this process? inputs are highly appreciated.

[Daniel_Gordon]

Agreed tree replication is notoriously slow for large amount of content. I'd look into package replication. Essentially create a package of the DAM content you want to replicate on the author instance and then replicate the package, it will be significantly faster. Unsure why content fragments would be so much slower. One thing to watch out for when doing package replication is dispatcher cache invalidation and replication status of assets. See ACS Commons feature: https://adobe-consulting-services.github.io/acs-aem-commons/features/package-replication-status-upda... and https://adobe-consulting-services.github.io/acs-aem-commons/features/dispatcher-flush-rules/index.ht...

[mohanb]

We tried both activate tree and package replication approaches. But overall time taken is same. Is there any configuration change/ fine-tuning to be done for package replication process?

[MC_Stuff · Accepted solution]

Hi Mohan,

Content fragment is also has asset/resource and should not take time.  Can you take a thread dump[A] when it is activating the content fragment and see who is cuplrit by uploading the thread dump at http://fastthread.io/

[A]  https://helpx.adobe.com/experience-manager/kb/TakeThreadDump.html

Thanks,

[jessielouthan]

Commenting to see what the resolution to this issue is, as I anticipate our team having this issue in the future.