Publishing redirects config took 3 minutes while single redirect

[chI06]

In publishing instance, we have noticed that when we tried to publish Redirect configs it took 3 mins and it is causing slowness to the instance while if tried to for the single redirect it took 1 min. or less than a sec. Anyone experiencing this? Is this expected? 

[Ritesh_Mittal]

Hi @chI06 ,

Could you provide more details on the following?

• How many redirects are being published at once? Are you working with tens, hundreds, or more redirects?
• Is the publishing instance under heavy load, particularly in terms of CPU, memory, or disk usage during publishing?
• Are the redirects simple URL mappings or do they involve more complex rules (e.g., regex)?
• Are there many redirects already configured or a large repository in general?
• Are there workflows or replication processes that are triggered during the publishing of redirects?

Possible Causes:

Publishing multiple redirects at once typically takes longer than a single redirect due to increased overhead, such as validation and processing of each redirect. If redirects affect cached content, Dispatcher cache invalidation can also slow things down. A large repository might need extra indexing or validation when bulk publishing, and server resource contention (high CPU or memory usage) could also contribute to delays. Additionally, replication of redirects to other instances can introduce extra time, especially if workflows or event listeners are involved.

it’s normal for bulk publishing of redirects to take longer than publishing a single one. However, 3 minutes for multiple redirects might indicate a performance issue or resource bottleneck that should be addressed.

Meanwhile, you also can -

• Monitor system resources (CPU, memory, disk usage) during publishing to identify if the system is under heavy load.
• Check caching and ensure that cache invalidation (especially Dispatcher cache) is being handled efficiently.
• Optimize the redirects by simplifying rules if possible.
• Test publishing in smaller batches to see if this reduces the publishing time.
• Review workflows or event listeners that might be affecting the publishing process.
• Check replication logs to identify any delays during replication.

Thanks

Ritesh Mittal

[sherinregi]

Hi @chI06 

How many redirect configs you have in the configuration and are they simple ones or includes patterns etc. Are you observing it every time you publish, check replication queues once and verify its idle and not blocked.