Is this really the version you are looking for? Kentico Xperience 9 Documentation is no longer updated. Use the switcher in the header to choose your product version.
Storing a large amount of content in the content tree can have a significant impact on website performance. You can set up archival of outdated pages in your system so that you reduce the number of pages in the content tree.
We recommend the Archival section in the content tree approach for most projects, including projects with large amounts of pages (hundreds of thousands). For extremely content-heavy projects, consider using module classes or custom storage.
You can create a special section in the content tree into which you'll move outdated pages. An even better approach is to keep the archived pages in the same section and creating new sections for new content — structured by years, for example.
When using this approach, the listings you use to display published pages need be configured to only to load data only from specific sub-sections of the content tree. For example, in the following structure:
Instead of displaying all the years in a single listing, individual web parts could be configured to cover only the pages stored under a specific year. You can configure this using the Path property.
Note: moving large sections of pages in the content tree is a performance demanding task. Make sure you don't perform the operation in peak hours.
You can move the main data stored in the archived pages into .
You can use the API to retrieve outdated pages and their related objects and store them in a custom storage. For example, you can serialize the data into an XML file.