Kbase P9992: What performance effects are there if -spin is set on only one database and not on another database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
03/05/2011 |
|
Status: Verified
GOAL:
What performance effects are there if -spin is set on only one database and not on another database on the same server?
GOAL:
Effects of -spin
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
If -spin is set on one database and not on another on the same server, what should be seen is better performance for the database with -spin set than for the other database - but this will depend on the respective structures of the databases, types of clients, etc.
If -spin is set for both databases, then the extra CPU usage would have to be taken into account when working out what performance you can expect and should be aiming for.
Without measuring and comparing, there is little else that can be said about this kind of situation.
Evaluate the -spin values through the PROGRESS Monitor (PROMON utility) R&D options. The -spin parameter controls the performance indicator called resource waits. By setting the -spin value higher, you can reduce the resource waits. Note that when setting the -spin value higher ceases to reduce the resource waits, continuing to set it higher can adversely effect CPU usage. To view the resource waits value:
1. Access PROMON and enter R&D at the main menu.
2. Choose option 3. Other Displays, then choose option 1. Performance Indicators to view the resource waits. Resource waits is the last item reported in the listing.
Evaluate the CPU usage using system utilities such as sar and vmstat.
Please note that indepth performance tuning generally will require a consultant on site, and falls outside the scope of Technical Support.