Being Proactive about Windchill R10 Performance

[vaillan]

There are multiple root causes of performance problems most are caused by problems in one or more of the following categories:

1. Configuration 
   • key wt and db properties files are 'ok' for performance
2. Database
   • There is 'enough' memory and the SQL is tuned and running quickly
3. Bugs
   • The software performs an operation in a way which is not optimal
4. Miscellaneous
   • There are numerous other but relatively rare types of problems which can cause performance and stability problems a few of them are:
     1. Customizations
     2. Hung Infrastructure component like a SAN drive or corporate LDAP
     3. Network problems (which are often sporadic)
     4. Server Machine problem,

Being proactive to me in terms of Windchill performance and stability means having the environment setup as well as possible, a monitoring solution in place and knowing what to do when there is a problem.

Proactive Steps which could be taken

• Run the Windchill Configuration Assistant See Chapter 1 Using WindchillWindchill ConfigurationConfiguration Assistant to Configure Windchill
• Run the Windchill Client Inspector
• (new article as of Oct 2012) Apply the indexes from the article: List of Recommended Oracle indexes to improve performance in Windchill 10

Proactive Monitoring:

• (Best) Install and use the Windchill System Monitor link1 & link2
• Check for long running operations using the Top SQL Sample Intervals
• There are other ways to monitor Windchill also, one which is relatively manual is to use the MethodServerSummary lines
• Database monitoring, there are also multiple ways this can be done.  Ideally there would be a DBA who does responsible, but using the gather info script or using the Oracle OEM are also options
  • A disproportionate number of Windchill performance problems result from under performing SQL statements
    

When there is a problem

• Technical Support has a group of people who specialize in diagnosing and resolving performance problems.  Opening a performance case is the best way to get their assistance. When the case uploading the 'Performance' data either using the System Configuration Collector or ensuring that the wt & db property files along with an Oracle report are part of the case along with an good description of the problem and any MethodServer logs which might be related; are the best ways for the TSE to start analyzing the problem