MCMS Performance - Best Practices
To avoid competition for resources among applications, it is important that you keep MCMS on dedicated servers. Instances of SQL Server should be installed on their own computers as well. This will avoid the applications and services competing for CPU and memory.
To know more about Caching read Enhancing Performance with Caching.
Make resources as minimum as possible to increase the performance of the site. Resources such as images, sound clips, and video clips can have a large impact on your Web site's performance. As a general rule, you should avoid using large resources. Compress resources whenever possible. For example, for pictures, use .jpg images instead of .bmp images. Also, unmanaged resources are not part of MCMS, you can achieve performance improvements by using them.
So it's better to make batch content updates as much as possible.
Database performance will decline during background processing. Therefore, as a general rule you should schedule background processing for non-peak times to reduce the chance that it will affect your site performance.
|Managing IIS||On a read-only site, remove HTML packager ISAPI filter.|
|SQL Server||For optimal performance, the databases should be separated from their transaction logs on different physical drives to prevent resource conflicts. For more information about SQL Server performance tuning, go to Optimizing Database Performance.|
|Design time Performance|
|Custom Property Searches|
Design such that, the total number of posting searched using custom property is less than 5000. It is better to have lesser that 500.
|Site Partitioning||Very large MCMS sites that contain many postings (which has more than 20,000 postings) should consider whether it is possible to partition the site into a series of smaller sites to get optimum performance.|
This is a summary from Performance Planning and Deployment with Content Management Server 2002.
Also Stefan has posted two less known performance issues caused by in-proper use of publishing API in his article.