Scaling Content Manager Server
You can improve SDL Tridion Sites performance, by installing a Content Manager software component on a separate machine (scaling out), or the same component on multiple machines (scaling up). Most of these components require Content Manager and any local software components. You must install all components locally on the target machine.
- Network Load Balancing and Server Clustering
SDL Tridion Sites supports Network Load Balancing and Server Clustering. - Installing database server on a dedicated machine
Except in a single-machine setup, always install the Content Manager database on a separate machine. Preferably, this should be a machine with at least 2 GB of RAM that scales up easily, has multiple processors, and has network access in the Gigabit range. Set the default network protocol of the machine to TCP/IP (if you use SQL Server, use the Client Network Utility to do this). - Multiple Content Manager instances and an Oracle RAC setup
If you use Oracle with RAC (Real Application Clusters), you can achieve (application-level) load balancing across your database instances. - Installing Publisher on a dedicated machine
You can install the Publisher on one or more dedicated machines. On a dedicated machine, you can configure the Publisher for a multiprocessor machine, or increase the number of Publisher threads. You can also create Publishers that only accept content from certain Publications or Publication Targets, or with a certain Publish Priority. - Upscaling or outscaling Workflow
You can upscale Workflow (by configuring multiple threads for the Workflow Agent) or outscale Workflow (by installing a Workflow Agent instance on one or more dedicated machines). - Upscaling or outscaling the batch processor
The batch processor is a software component used for performing operations on multiple items at the same time, for example, deleting 10 items in one go. Especially if your custom implementation performs such batch operations often, upscaling and/or outscaling the batch processor may be worthwhile. - Installing Search on a dedicated machine
To optimize search performance in an enterprise environment, you need to install Search on one or more dedicated machines. - Configuring a shared network temporary location for uploads to the Core Service
Before files uploaded to Content Manager are saved to the database, they are placed in a temporary location. By default, this upload location is on the machine where the Content Manager server is installed. But in an outscale scenario, with multiple Content Manager instances running in parallel, all instances must save their uploads to a single temporary upload location: a network folder that all instance must have write access to. This task explains how to specify such a location. - Configuring a temporary location for uploads to the Core Service in the Amazon Cloud
You can use Amazon's S3 storage server for the temporary storage of binaries that users upload to the Core Service. - Configuring high-availability storage for Import Export service items
To ensure that import packages, export packages and undo packages are available to all Content Manager machines in your scaled-out Content Manager instance, edit the Content Manager configuration file, Tridion.ContentManager.config. - Exporting and importing Content Delivery information between Topology Manager instances in a scaled-out setup
If you have multiple Topology Manager instances running side by side, say, in a scaled-out or hybrid Cloud setup, you may want to transfer Content Delivery environment definitions between them. After the transfer, you can actually recreate the Content Delivery environment(s) in your target instance.