Application Slow start due to init processor reading high latency web databases

[zhankezk]

Can't exactly say this is an issue, it could be a feature request as well.

Basically we have 2 web databases, one of them is in a GEO-distributed remote region which has 200 ms latency with the main CM instance.

We uses publishing service for publishing tasks since out of box publishing take 8+ hours to complete a site smart publish. But remote database definition is still added in CM for handling event queue.

We noticed after a while, CM takes around 15 mins to start up every time it restarts. With some profiling and traces, we identified the bit that takes most time and blocking all requests is the processor:
<processor type="Hi.UrlRewrite.Processing.InboundRuleInitializer, Hi.UrlRewrite" />

After removing this processor, CM startup time is back to normal.

In the code, it go through all the databases and caches the inbound rules. Remote web database is one of them.

Since this is authoring and looks like this is for Site visit, we assumes it should be fine to disable this processor on CM. We need more time to validate but not sure if anyone can confirm this?

Also not sure what's the best way to handle this properly going forward. What's your view?