Skip to main content

Slow DB Performance on Content Manager Writes


The issue below took me a good 6 hours to fix. Hopefully it will save somebody that time, so here it is:

My Tridion 2011 SP1 HR1 Content Manager was getting hit by a very peculiar performance issue – when saving, creating or deleting any item, the operation would be very slow (5+ seconds). This was on a controlled environment (my VMWare) with nobody else on the system. The issue was manifesting in both the CME and with API (Core Service and TOM.NET).

After checking the usual culprits (disable Event Systems, disable CME extensions, execute sp_updatestats, rebuild all tables index, repair SDL Tridion CM, uninstall/install CM), I finally noticed in the Tridion event log the following line (in fact there were hundreds of these warnings):

Unable to notify "T2011SP1". Reason: The requested name is valid, but no data of the requested type was found
Component: Tridion.ContentManager
Errorcode: 0
User: T2011SP1HR1\MTSUser

The host T2011SP1 is the old hostname of my VMWare. I make a habit that I rename the servers names to reflect the version of Tridion I’m running. This immediately led me to go to my Tridion_cm database and delete the entries from QUEUE_CONSUMERS and QUEUE_FILTERS tables that have HOST = ‘T2011SP1’. A less drastic measure would have been to simply set their respective column IS_ONLINE = 0.

Restarted my Tridion * services, shutdown the Tridion COM+ application and magically performance was back as it used to. Now I can batch update existing items via the Core Service in about ~0.25s per item.

What seemed very strange was that the ‘write’ operations were being notified to the other CM instances present in the QUEUE_CONSUMERS table. That table contains messages of type Publish, Deployer, Workflow, and Search. I guess it was the Search that was being updated… not sure.

Comments

Anonymous said…
Had the same problem when trying to put items in the publishing queue with the core service. Removing these speeded things up a lot!
Unknown said…
Mihai, I followed your steps above and worked like a charm!! Great post!

Popular posts from this blog

Toolkit - Dynamic Content Queries

This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio

A DD4T.net Implementation - Custom Binary Publisher

The default way to publish binaries in DD4T is implemented in class DD4T.Templates.Base.Utils.BinaryPublisher and uses method RenderedItem.AddBinary(Component) . This produces binaries that have their TCM URI as suffix in their filename. In my recent project, we had a requirement that binary file names should be clean (without the TCM URI suffix). Therefore, it was time to modify the way DD4T was publishing binaries. The method in charge with publishing binaries is called PublishItem and is defined in class BinaryPublisher . I therefore extended the BinaryPublisher and overrode method PublishItem. public class CustomBinaryPublisher : BinaryPublisher { private Template currentTemplate; private TcmUri structureGroupUri; In its simplest form, method PublishItem just takes the item and passes it to the AddBinary. In order to accomplish the requirement, we must specify a filename while publishing. This is the file name part of the binary path of Component.BinaryConten

Scaling Policies

This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the