"I feel the need, the need for speed!"
The following checklist (with links to resources and reference articles) will help you to achieve the goal of keeping your systems and deployments working at peak performance and efficiency and will reduce the number of problems that can be experienced while working with TEM.
* For any item with an asterisks by it, please refer to this Wiki article for more information:https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Endpoint%20Manager/page/Performance%20Configurations
Please feel free to comment back to this blog post on items you have tried or implemented and which have increased performance in some way.
The Application Server and Database
- Ensure enough system resources have been allocated to the TEM Server and database machine(s) for the size of deployment you are managing (http://www-01.ibm.com/support/docview.wss?uid=swg21505691)
Use newer and fuller versions of SQL Server. SQL Server 2008 R2 (Standard and Enterprise) offer the best capacity and performance. MSDE and SQLExpress are not supported in production environments.
Configure RAID cache performance *
Configure RAID Array for Read/Write Speed *
Perform file and disk clean up on the server machine (Windows Disk Cleanup utility). Delete any very large files and files that are no longer needed (Google TreeSize).
Run a defrag job on the disks that the TEM server and SQL Server applications are running from to increase performance of the hard drive's disk seek time (Disk Defragmenter).
Run CHKDSK to check and repair any bad parts of the disk.
Use TEM Relays to reduce TEM Server load *
Lower heartbeat interval *
Lower TEM Console refresh interval *
Configure virus scanners not to scan TEM Server / TEM Relay folder *
Move TEM Server program files to different drive than SQL Server database *
Do not use file indexing or file compression on TEM Server / TEM Relay computers *
Ensure that the SQL Server process is not allowed to consume all of the of the Server's memory. There needs to be enough memory available for the server OS to operate as well as the TEM server application.
Verify that the re-indexing jobs are continuing to run without a problem (Found in the Job Activity Monitor for the BFEnterprise database). If the re-indexing job is continually failing then the problem causing the failure needs to be resolved.
Change SQL Server transaction log type to "Simple" *
The Deployment and Network
- Use TEM Relays to reduce total network load (a properly configured relay architecture is key for efficiently managing larger deployments) *
- Use high speed network connections for TEM Server/TEM Relays *
- Use TEM Management Rights *
- Always use the "Stagger action start times..." feature *
- Use more powerful TEM Console computers *
- Delete closed/expired actions (Helps to improve Console load times) *
Deploy patching actions using non-master operator accounts. Reserve the master console operator accounts for taking actions that administrate and configure the deployment.
Limit baselines and baseline actions to at most 75 components.
Close open actions that are not longer needed *
Test custom content in a test environment before deploying it to a production environment. Custom relevance or actionscript that contains errors or is not tested has the potential to hang the clients' evaluation loops blocking the client from reporting in, accepting actions, and processing actions.
There is a way to increase the amount of CPU the client uses (to http://www-01.ibm.com/support/docview.wss?uid=swg21505852
). In some circumstances you may want the client to evaluate its content quicker and get through its evaluation loop faster. However, this is typically not done as it may disrupt the end users experience.
Tivoli Endpoint Manager Support Team!