Scroll Apps Migration Hub

Conversion Performance Tuning

Converting a space to Scroll Content Manager is a technically complex operation, and in case of large spaces with many pages, this may take some time to process.

Here are a few things you can do or check in order to speed up conversion.

Convert One Space At A Time And Convert Only

The most important recommendation is to convert one space at a time.
Do not convert multiple spaces as this may severely degrade overall performance of your instance.

And do only convert one space at a time, do not run any CCMA Cloud migrations in parallel, as CCMA is also know to consume a lot of system resources.

Cf. Why You Can't Convert Multiple Spaces at Once

Cache Management

Ensure your caches are properly configured:

<BASE-URL>/admin/cache/showStatistics.action#fullView

Assume the largest space to convert has #P number of pages, #V number of versions to convert, and #L number of languages to convert, we recommend to set them to at least the following values:

Some of these caches may not be displayed on according UI as they are still empty on your instance.

Cache

Recommended Size (Maximum elements)

Pages

3 x #P x #V x #L

Page Children

2 x #P x #V x #L

Page Ancestors

2 x #P x #V x #L

Attachment IDs

5 x #P x #V x #L

Spaces (by key)

more than the total number of spaces

Content Objects

3 x #P x #V x #L

Content Attachments

3 x #P x #V x #L

Content Properties

5 x #P x #V x #L

Plugin Settings

10 x number of spaces

Inherited Content Permission Sets

3 x #P x #V x #L