ADSM-L

ADSM NT Server Performance - Correction

1999-08-31 13:12:03
Subject: ADSM NT Server Performance - Correction
From: Joshua Bassi <jbassi AT GLORYWORKS DOT COM>
Date: Tue, 31 Aug 1999 10:12:03 -0700
All,

I received some additional information regarding the NT ADSM
server's multithreading capabilities and I thought I would
share it with the group.

The ADSM server on NT does multithread, just not well, hence
the  recommendation to restrict the ADSM server to UP machines.
The ADSM NT server is and always has been multi-threaded, so
different threads within the server can get dispatched on
different CPUs at the same time.  The dispatching is of course
done by the operating system.  However, within the ADSM NT
server, there are resource contentions that occur, and that
actually degrade throughput when multiple threads are contending
for those resources simultaneously.  An easy way to prevent
those contentions and the subsequent degradation, is to restrict
ADSM to run on only one processor, i.e.. allow the operating system
to only dispatch threads from the ADSM server process on one CPU.

That said, many of these contentions have been resolved in the
Tivoli Storage Manager Version 3.7 release due to be available
soon.  Hence the reasons for restricting ADSM to run on a single
CPU will disappear.


Joshua S. Bassi
Storage Management Team Lead
Tivoli Certified Consultant - ADSM V3
IBM Certified Specialist - AIX and
Mid-Range Storage Technical Solutions
Dickens Services Group
(404) 386-9848
jbassi AT gloryworks DOT com
www.TeamDSG.com
<Prev in Thread] Current Thread [Next in Thread>
  • ADSM NT Server Performance - Correction, Joshua Bassi <=