Content structure and publishing

Overview

This section covers Magnolia CMS structure, focusing on optimizing the use of Apache Jackrabbit as the repository implementation. It also covers ways to improve publishing performance, the Synchronization module for selective content publishing, and best practices for structuring a JCR workspace to avoid performance issues.

Tuning tips - Content structure and publishing

  • Repositories and workspaces

    • The JCR standard API is used for content repositories. Don’t change data by bypassing the API, as this can cause integrity issues.

      For more, see JCR standard API for content repositories.

    • Best practices for structuring JCR workspaces:

      • Limit child nodes to under 500 for any parent node.

      • Use time-related content folder structures (for example, /<year>/<month>/<category>/<page>).

        For more, see Structuring your JCR workspace.

  • Optimizing publishing performance

    • Publishing pages separately.

    • Using itemsPerRequest to reduce publication requests.

    • Optimizing ordering on the public instance.

    • Optimizing dead nodes in PostgreSQL.

      For more, see Publishing performance.

  • Swift publishing

    • Scale publishing efficiently using the Swift publishing module.

      For more, see Swift publication.

Subpages in this section

Feedback

DX Core

×

Location

This widget lets you know where you are on the docs site.

You are currently perusing through the Performance tuning guide docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules
6.3 beta
X

Magnolia 6.3 beta

Magnolia 6.3 is in beta. We are updating docs based on development and feedback. Consider the 6.3 docs currently in a state of progress and not final.

We are working on some 6.3-beta known issues during this phase.