
136 MetaFrame Solutions Guide
Interrupts
A defective device adapter can cause an excessive number of interrupts. This
severely degrades the performance of the system because most of the processor
time is spent handling interrupts. A moderately busy server (32-bit hard disk
adapter, network card, and about 12 users) will experience an average of about
100 interrupts per second. If the number of interrupts per second increases
dramatically without a corresponding increase in system activity, it could indicate
a hardware problem. To determine if there is excessive interrupt activity, monitor
the Interrupts/sec counter under the Processor object.
Context Switches
Device drivers perform context switches to switch between user and system level
processing. A poorly-written device driver can cause the system to make a large
amount of context switches. A typical value for context switches is 500 per second
or fewer. If the number of context switches per second is greater than 500, a
device driver may have built-in critical sections that are too long. To check the
server for poorly written device drivers, monitor the Context Switches/Second
counter under the System object.
Screen Savers
Screen savers, especially “busy” ones, can use a large amount of processor
resources and, in the case of an ICA connection, network bandwidth. If you plan
to use a screen saver, use a generic one and test it on the system before you
implement it.
To determine if a screen saver is using too much processing time, run the screen
saver on the console. Log on to an ICA Client and run Performance Monitor.
Monitor the %Processor Time counter under the Processor object. Note the
demand that the screen saver puts on the processor.
Memory
The factors related to system memory that can affect performance on a MetaFrame
server include:
K
Memory load
K
The system page file, Pagefile.sys
K
Memory paging
Komentáře k této Příručce