How Big Can CMS Infrastructure Get?

How big can a production CMS server get?

The short answer is as big as your blank check allows.

serverInfra

As you add users, workflow, translation, heavy publishing, and lots of opening/changing components, the CMS server size will inevitably increase.

Often times, multiple CM services are all enabled on one large machine for the enterprise, but the downsides of that are when one problem happens, all aspects of your CMS fail with it. Below I show what an infrastructure looks like that handles very large publishing loads and is scalable to add more load. The CMS also handles workflow services and translation integration with World Server.

You will have to click the image to open in a new window and zoom in to read the details.

Tridion PROD Infrastructure 2013

 

Turning on only the publishing and transport services allows you to move the rendering of pages (the publishing load causing performance hits seen to the CMS user) over to another server or pool of servers. This also allows your dedicated publishing servers to scale as publishing load increases. This means that if publishing isn’t keeping up with demand, you can spin up another machine and add it to the pool to gain throughput. The less time editors stare at “Waiting for publish” the more work they complete!

The advantage of doing this doesn’t stop at scaling. Now your users do not see a slowdown in system performance when publishing. If publishing needs restarted, then the users can still work in the CMS and publishing resumes when the server comes back up. The publishers can be restarted in series to allow for zero downtimes.

In addition to the dedicated CMS publishers, you can also repurpose a dedicated DR (Disaster Recovery) CMS box to also pick up additional capacity when not in use. If you need the DR server it is as simple as starting the rest of the services and it is back fully purposed as a DR CMS environment in minutes.

As for the DR environment, it’s a fairly simple setup. Log shipping is setup between the Live CM database and the DR CM database. If DR environment is needed, you can simply turn off the log shipping and the DR CMS will start working.

There are some additional ways to scale out as needed. If you have a lot of workflow processes running you can have a dedicated machine just to run your workflow processes. This has similar pros to the publishers.

All static files go to central data center NAS servers which serve the individual web servers with the static content.

The size of the CMS machines are fairly large machines in the Tridion world. For production, we have 3 dedicated publishing servers with 48 CPUs and 256GB memory each. This allows for an optimal 108 rendering threads and 72 deployer threads for high-speed mass publishing.

 

 

 

 

Use GUI Extension to Solve for Content Re-Ordering

GUI Extension: Components Re-Ordering Dialog

  • SDL Best Practices recommend not localizing pages.
  • We originally used Container Components so that Editors can re-order components without needing page localization.
    • The use of Container Components introduced other issues as explained in this blog about Container Components.
    • The solution outlined below does not rely on containers.
  • SDL can store additional data on each component using Application Data. Application Data is applied to items across the blueprint and don’t require items localization.

Application Data to store components order

  • A GUI extension can update page application data to store components ordering.
  • Page Application Data is naturally local to each page
  • At publishing time, Application Data is also published within the page.
  • The Web Application can use the Page Application data to retrieve the components ordering and show them in the right order.

Known Issues

  • Where used does not show where the data has been localized and changed. Here are some possible solutions:
    • The GUI extension could flag these application data changes and display them back through the GUI
    • The GUI extension puts a component on the page with the ordering data and localize that component.
    • Where use functionality is extended to look for the page application data.

The diagram below shows how the components involved in the solution work together

fOeiCBr6oYK-

Problems with Container Based Content Model

Containers are a common approach when designing CMS content models. They allow Authors and Content Editors to organize content hierarchically. While containers allow contributors to group, reorder, and organize content easily, they also add a lot of dependencies to the content across the system.

Containers add complex scenarios for simple tasks, including:

  • Publishing
  • Delete + Unpublish + Localize + Unlocalize
  • Workflow
  • Translation

Effects of using a container model:

  • “Where Used” filters are used extensively
  • Large amount of content dependencies lead to performance issues
  • Large amount of content manager transactions while publishing to ensure content integrity lead to stability issues
  • Multiple Database Transactions during Publishing
  • Complex content unpublish and deletion
  • Complex Experience Manager implementations (Experience Manager is not designed to use Containers)

Content Integrity Example:

In the scenario below, Tridion will attempt to maintain content integrity by publishing all pages using component instances. This example would cause a link propagation issue if the following conditions were met:

  1. Text Block – With image component is published within a page
  2. Application Include Container component is published within a page
  3. Buttons Actions tray component is published within a page
  4. Button App Include is published within a page

containerImage