Numerous NS Console functions very slow

book

Article ID: 181605

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server)

Issue/Introduction

 

Resolution

Question
Customer is seeing extreme slowness with many of the Altiris Console functions. For example:

The Software Portal screen takes 10 to 12 minutes to open.

The CMDB Clean-up Ownership task times out prior to completion. Running the “exec spAC_CleanupOwnership” through query analyzer took 103 minutes to run.

A Barcode policy was timing out.

The NS seems to be processing NSEs very well but many things performed in the console are extremely slow.

Answer

These processes are heavy TEMPDB related. For instance: A single connection via the software portal creates 3 temp tables. If a large number of people are accessing the software portal at any give time and the TEMPDB is not configured properly, SQL may not be able to write to the drives quick enough.

What we found was that the TEMPDB was located on a RAID 5 drive set with the Altiris Database. Perfmon showed the Ave. Disk Queue Length to be close to 100. It was very apparent that there was an I/O bottleneck.

A new SQL 2005 server was built with a RAID 10 configuration for the Altiris Database and a mirrored drive set for the TEMPDB and the Altiris database was migrated off the NS to this off box SQL Server. Once this was done, these functions that were taking minutes and hours to run, completed in seconds.

Below is a URL that has good information on configuring the SQL server:

http://www.tek-tips.com/faqs.cfm?fid=5747

The various parts that we will be addressing are the binaries (the actual exe and dll files of the server), the system databases (master, msdb, model), the user databases data files (all the databases you put on the database), user database transaction logs, and tempdb.  (When it says RAID 5 a RAID 4 or RAID 5+1 can also be used as well.  I am simply choosing the less expensive option for my example.)
  • Binaries - I usually place the binaries on the OS drive.  For the most part they are read from once (when the SQL Services are started) and not again.  The only thing that will be written here are the error log and sql agent log files.
  • System databases - Each system database has different requirements.  Overall a RAID 5 is best.
    1. master - The master database is mostly read, seldom write.
    2. msdb - The msdb database is about 50/50 read/write.
    3. model - The model database is ready only when a new database is created or the SQL Service is started.  It should almost never be written to.
  • User databases data files - Most databases are mostly read, seldom write.  Because of this a RAID 5 array is the best option.  If your database is never read from and written to often (for logging for example) then a RAID 0+1 would be your best option.
  • User databases log files - Transaction Log files are very write intensive.  They should be placed on a RAID 1 or RAID 0+1 array.
  • tempdb - Tempdb is very write intensive.  It should be placed on a RAID 1 or RAID 0+1 array. (On most any SQL Server the data file and log file for the tempdb database can be placed on the same array.  On SQL Servers with trully massive tempdb usage you may want to split the tempdb data file and log file onto thier own RAID 1 or RAID 0+1 arrays.)