H
huangbaili
Unregistered / Unconfirmed
GUEST, unregistred user!
Some administratorsdo
not understand the processor Utilization statistic in
MONITOR.NLM, and they believe that the higher the percentage, the worse
NetWare’s performance will be. This is entirely false. If you watch the
utilization figure in monitor for only a short while you抣l realize that this
number spikes to 100% quite often. Even numbers averaging 60's or 70's may be
OK in some environments. However, high utilization that is a problem will
usually display these conditions: (1) Performance deteriorates noticeably;
some examples are listed here, (2) Utilization will peg at 100% for periods 15
to 20 minutes or longer, sometimes causing users to be dropped by the server,
(3) Logins take an extremely long time, (4) Applications fail or discontinue to
work, (5) File copies take too long to complete, and (6) Switching screens at
the file server console takes a long time. If you are not seeing these
conditions, your utilization may be normal. Baseline your server. Know what is
normal, and know the difference between a cosmetic problem and a true
performance issue.
Server utilization is defined as the amount of work the server isdo
ing with
respect to the maximum amount it could bedo
ing. Server utilization in NetWare
is measured as an amount of processor utilization. Processor utilization is
measured as a percentage of the time the CPU is currently active. NetWare
calculates the utilization value by taking the inverse of the percentage of
time that the CPU sits idle.
An example of a high utilization situation usually happens in larger
configurations at login time. When multiple logins are being processed by the
server, the decryption of the users passwords is very CPU intensive and a
utilization spike can be readily seen. Large mathematical formulas and
operations must occur to decrypt a password to allow the users to authen
ticate
into the network. If too many login processes are running at the same time then
the processor can fall behind. Logins will eventually complete, but the server
may experience
100% utilization while processing the requests to decrypt the password.
not understand the processor Utilization statistic in
MONITOR.NLM, and they believe that the higher the percentage, the worse
NetWare’s performance will be. This is entirely false. If you watch the
utilization figure in monitor for only a short while you抣l realize that this
number spikes to 100% quite often. Even numbers averaging 60's or 70's may be
OK in some environments. However, high utilization that is a problem will
usually display these conditions: (1) Performance deteriorates noticeably;
some examples are listed here, (2) Utilization will peg at 100% for periods 15
to 20 minutes or longer, sometimes causing users to be dropped by the server,
(3) Logins take an extremely long time, (4) Applications fail or discontinue to
work, (5) File copies take too long to complete, and (6) Switching screens at
the file server console takes a long time. If you are not seeing these
conditions, your utilization may be normal. Baseline your server. Know what is
normal, and know the difference between a cosmetic problem and a true
performance issue.
Server utilization is defined as the amount of work the server isdo
ing with
respect to the maximum amount it could bedo
ing. Server utilization in NetWare
is measured as an amount of processor utilization. Processor utilization is
measured as a percentage of the time the CPU is currently active. NetWare
calculates the utilization value by taking the inverse of the percentage of
time that the CPU sits idle.
An example of a high utilization situation usually happens in larger
configurations at login time. When multiple logins are being processed by the
server, the decryption of the users passwords is very CPU intensive and a
utilization spike can be readily seen. Large mathematical formulas and
operations must occur to decrypt a password to allow the users to authen
ticate
into the network. If too many login processes are running at the same time then
the processor can fall behind. Logins will eventually complete, but the server
may experience
100% utilization while processing the requests to decrypt the password.
