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

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven