Slow Performance When Opening Large DITA Maps with Many Key References

[mikejohnson]

Hi everyone,

I've noticed that working with large DITA maps containing many topics and key references can sometimes feel slow, especially when opening a project for the first time or after refreshing references. In some cases, the editor takes a while to fully load content, resolve keys, and update related links.

It would be helpful if Oxygen XML provided more visibility into what is happening during the loading process, such as a progress indicator showing which resources are being processed. This could make it easier to identify potential bottlenecks and reassure users that the application is still working in the background.

For teams managing large documentation sets, even small improvements in loading feedback and performance diagnostics could make daily workflows smoother and more efficient.

Has anyone else experienced this with larger DITA projects?

[Radu]

Hi Mike,

Thanks for the feedback!
A DITA Map can be opened both in the DITA Maps Manager view and in the main editor area. And indeed for the DITA Maps Manager view we do not give indication about what's being done when the map is being opened.
Are you opening the maps from the local disk or from a remote storage server like a CMS?
To get an idea about the magnitude, about how large are the DITA Maps you are working with? How many submaps, how many referenced topics?
How much time does it take on your side to open such a DITA Map in the DITA Maps Manager view?

Regards,
Radu