TECHNICAL INVESTIGATION (the geek stuff):
OK, I resorted to looking at the Windows Performance Monitor. With OOTP4 running (on the startup screen, the following specific measurements are impacted severely:
Processor / %Processor Time - runs consistently at 100%
(near 0% without OOTP)
Processor / %User Time - runs about 95% on startup screen, down to about 70% after hitting "Let's Play"
(near 0% without OOTP)
System / Processor Queue Length - ranges from 3 to 12 with OOTP running, avg is 4+
(ranges from 1-2 without OOTP but while using other apps)
This last one is important, per Microsoft mgmt console help (text reproduced below)
Investigating processor bottlenecks
A processor bottleneck develops when threads of a process require more processor cycles than are available. Long processor queues can build up and system response suffers. The two most common causes of processor bottlenecks are CPU-bound programs and drivers or subsystem components (typically disk or network components) that generate excessive interrupts.
To determine whether a processor bottleneck exists due to high levels of demand for processor time, check the value of the System\ Processor Queue Length counter. A queue of two or more items indicates a bottleneck.
- - -
OOTP Developers - any thoughts on this? Should I provide any other information?
__________________
Right Field Sucks!
|