Hello, We are noticing slowness during Bulk Publishing. There are generally 100 assets at a time. Sometimes publish server is inaccessible and restores back once queue is cleared. During publishing, we have 2 events Assets incoming from Author Dispatcher Flush We have enabled Batch processing for Replication Agent, but no luck. Binaryless replication enabled. Requesting suggestions on how we can improve this?

aanchal-sikka

Community Advisor

Solved

Publish Instance inaccessible during Bulk Publishing

Forum|Forum|1 year ago
September 27, 2024
3 replies
1587 views

Hello,

We are noticing slowness during Bulk Publishing. There are generally 100 assets at a time. Sometimes publish server is inaccessible and restores back once queue is cleared.

During publishing, we have 2 events

Assets incoming from Author
Dispatcher Flush

We have enabled Batch processing for Replication Agent, but no luck. Binaryless replication enabled.

Requesting suggestions on how we can improve this?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by joerghoh

please run a number of threaddumps (eg. 10 dumps with 1s delay between them) on publish during such a situation, that should allow you check details.

EstebanBustamante

Community Advisor and Adobe Champion

Hi,

Is this happening on an On-premise instance, It is AMS? Are any useful info in the logs?

Esteban Bustamante

aanchal-sikka

Author

Community Advisor

@estebanbustamante

This is an AMS instance.

I have following improvements is mind, please let me know if they make sense and if there anything else we could do?

To use MCP based approach like Asynchronous publishing upto few assets then synchronous.

ReplicationOptions options = new ReplicationOptions();
options.setSynchronous(true);
replicatorService.replicate(session, ReplicationActionType.ACTIVATE, payloadPath, options);

Using TTLs & disabling dispatcher flush agent

Any thing you can think of that could help with optimizing resources?

Aanchal Sikka

EstebanBustamante

Community Advisor and Adobe Champion

I think something is happening on the publisher's side. I would start by checking the JVM on the publishers, as Jorg has pointed out. You should take those dumps to see if anything is consuming memory.

Another thing I would check is indexing. Look for any unusual behavior around indexing with each activation. You should be able to see when the last indexing and re-indexing occurred and verify if everything is okay.

Esteban Bustamante

joerghoh

Adobe Employee

Where does the slowness happen? On author or on publish side? And when you mention "slowness", does it only affect the respective part of the replication (sending or receiving) or does it affect the entire instance and other activities as well?