Client Management Suite

Hello.

When I installed cms 7.1 I always thought it was slow but now it's hindering me doing my job due to the console hardly loading and if it does it takes about 10 attemps and an equal amount of page refreshes. I do run the console directly on the server becuase it only works in IE8 all the machines around my work have IE10

The server it runs on is quite high spec although the sql server runs on a vm and is a bottleneck.

Is there anything I can do to bring it back to life?

I already have indexing on the sql database. At present the database is 20gb, the endpoints we have are about 300, Maybe there is something i can do to reduce the database size and increase speed.

I have seen SP2 around with the MP1 update, will this help with the performance issues?

Thanks in advance.

This might help: http://www.symantec.com/docs/TECH200276

Thanks for that, it pointed me to the below url, it doesn't say how he did it or if it works with 2008 r2 x64 cms 7.1 sp1.

Creating new IIS application pools - the magic solution to SMP 7 slow console operations?

https://www-secure.symantec.com/connect/blogs/creating-new-iis-application-pools-magic-solution-smp-7-slow-console-operations

Has anyone tried this? Is it a solution?

That guidance has been pulled.  Symantec no longer supports that configuration even though the original documentation was writted by a Symantec employee.

Try this:

https://www-secure.symantec.com/connect/blogs/performance-tuning-smp-71sp2

Thanks, for the reply. two questions tho. Firstly I'm still using SP1 so does the NTLM setting still apply?

2nd, my SQL server has 4 cores so should I impliment the sql tweek mentioned on the above url.

You should still be able to make the NTLM change but your best course of action is to get SP2 installed along with all of the Rollup updates.  I think that the most current version right now is 7.1 SP2 MP1.1 Rollup 5.  You're at least 6 versions behind.

I am amazed at the speed of our SMP7.1 console, my previous implementation for my old company's console performance was dog slow, and down right irritating. Like you, my old company's cmdb was hosted in a VM.

This is what I have setup and it has been running super.

1) SMP on a physical (although I think this can be Virtualized)

2) CMDB is on physical (i think this is a big factor)

My winning configuration:

1) Creating IIS pools is a must!!!

2) HighTower's  SQL settings, NTLM (configuration is debatable)

3) be on on the latest version.

4) Create a Schedule to defrage your SMP daily!! (do it in the evenings)

5) Create a schedule to defrag and reindex your sql server daily!! (evenings)

6) run repair every 6 months or so.

7) if you can put your SQL on physical, if you can't virtualize your smp and host your cmdb on a physical.

Symantec stated somewhere here in Connect that the split IIS app pools can cause major problems during upgrades.  Use that at your own risk and be sure to revert everything back to the standard pools before applying any updates to your SMP.

Good to know HighTower, thanks!

Hi, thanks for your help so far. I have implimented the NTLM setting.

To imporove this further I will go down the upgrade path to SP2, then all the additional MP updates.

Is there an upgrade guide I can follow to do this, or is it easy to do by the SIM

Thanks in advance.

Here is the Upgrading to ITMS 7.1 SP2 – MP1.1 – Best Practices 

 http://www.symantec.com/docs/TECH197966

Def looks like a the known issue with your version.  FYI :

               http://www.symantec.com/docs/TECH46681

I would look into implementing these SQL setting, I have noticed around 50 % increase in console reposonse on new Installations of ITMS

Max Degree of Parallelism

Set between 2-4, do not exceed number of physical cores.

Enable the option to Optimize for Ad hoc Workloads

ITMS has high degree of Ad-hoc/dynamic queries that are non-cacheable

Read Commit Snapshot

ALTER DATABASE Symantec_CMDB SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK AFTER 30 SECONDS.

Maximum Server Memory

            Leave enough memory for OS and tools SSMS.

            Ex:  Set 4-6 GB less amount of RAM installed

Cost Threshold for Parallelism

            Increase to 10.  Reduce chances of plans going to parallel

Thank you all so much for the replies. They have helped me out considerably.

I had changed the below server settings which i instantly noticed an improvement with.

Reporting server, or parent server in a hierarchy:

    Enable Read Committed Snapshot mode (replace database name with appropriate name) using:

    alter database Symantec_CMDB
    set read_committed_snapshot on
    with rollback after 30;
     
    Enable the Auto Update Statistics Asynchronously setting in the Database Properties, Options page.

I have a query regarding the below database setttings:

Optimize for ad hoc workloads  - True

Cost threshold for parrelism - 20

Max degree of parallelism - 4

Set Arithmetic Abort Enabled to true

would  any of the four above settings effect any other databases which reside on a sql server?
Or are these settings good for any SQL 2008 Server's performance.

Thanks in advance.

Unless I'm mistaken you set these values per instance.  Best practice for SMP would be to have the Symantec_CMDB and associated databases in its own instance.