CPU Considerations when Evaluating SpectroSERVER Performance (Legacy KB ID CNC TS33787 )
Article ID: 51784
Updated On:
Products
Issue/Introduction
First, remember that the system's CPU may be busy, but it's not necessarily Spectrum taking the CPU. The Performance views in OneClick will show you the top ten CPU users, as will the command
/usr/ucb/ps -auxww
Top will give you the same kind of information. The Find Process utility on the toolbar of CDE also gives you that information. The executable is /usr/dt/bin/sdtprocess.
On Windows, you can simply pull up the Task Manager.
The SSPerformance model and VPSERVER collects information on SpectroSERVER CPU utilization, so that you can determine whether this is an isolated spike of CPU utilization or part of a trend or constant problem over time. CPU data is also collected if you run a health report.
First check to see that the CPU is not being used by some other application. If it's Spectrum, which application is using the CPU? Archive Manager? SpectroSERVER? AlarmView? The point is that it's not always the SpectroSERVER's fault.
After determining that the SpectroSERVER is taking all the CPU, find out what views are open, what clients are connected, and as much information abut the environment as is relevant. Run a moot trace (see the Threads link on how to run a moot trace) to see what the SpectroSERVER is up to. It could be that there is a loop causing certain inference handlers to make the same calls over and over. Check the VNM.OUT for error messages. Take a look at the types and number of SpectroWATCHs running. The bulk of the troubleshooting of CPU utilization is in identifying what is using the CPU.
Run a sizing. It could be that you have maxxed out your system. The CPU should be less than 80% utilized, and when we run a sizing, we assume 50% CPU utilization.
Finally, here's a blurb from the Performance Engineering page concerning Spectrum on multiple CPUs:
"The main SpectroSERVER process does not take advantage of multiple
processors due to our use of a threading system (moot) that is separate from
the native OS threads. That being said, some benefit can be derived from
adding a second processor due to other processes, such as Archive
Manager, being shuffled to the second processor by the OS. Testing that we
have done on multi-CPU systems indicates a gain of 10%-15% management capacity can be had from a second processor, and negative returns if any at all from additional processors after two. This increase in capacity could be much greater if many other applications are being run on the same machine."
Related Issues/Questions:
CPU Considerations for SpectroSERVER Performance
Problem Environment:
Also Reference: TS33775 How Polling and Logging Affect SpectroSERVER Performance
TS33776 - Threading in the SpectroSERVER
TS29131- Collecting & exporting SpectroSERVER performance data
TS30314- How do I get and run the VPserver SPECTRUM Performance tool?
Spectrum 8.1
Spectrum 9.x
(Legacy KB ID CNC TS33787 )
Environment
Component:
Feedback
