Hi Rob

Have you tried setting the compression to no? There is no need to use compression on a gigabit interface, it will only

slow the client down, and the wait time for the session will get higher.  

I would also try setting the tcpwindowsize higher. A Windows 2000 machine can handle a windowsize up to 2048, but I think between 512-1024 would significantly increase you performance.

-----------------------------------
Daniel Sparrman
Exist i Stockholm AB
Bergkällavägen 31D
192 79 SOLLENTUNA
Växel: 08 - 754 98 00
Mobil: 070 - 399 31D
192 79 SOLLENTUNA
Växel: 08 - 754 98 00
Mobil: 070 - 399 27 51

 
Rob Schroeder <robs AT FAMOUSFOOTWEAR DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
2001-09-28 14:33 EST
Please respond to "ADSM: Dist Stor Manager"

To: ADSM-L AT VM.MARIST DOT EDU
cc:
bcc:
Subject: performance question

I am running TSM client 3.7.2 on a Win2000 server with Service pack 2.  The
TSM server is Win2000 SP2 and using TSM 4.1.3.  I realize I need to upgrade
the client, but I that will not happen until next week.  My dilemma is
this: the server backs up to the TSM server directly to a DISK pool that is
quite large, the network is Gigabit, and this client is the only client
that is talking to the server.  There are no other applications running on
either server.  I would expect this baby to scream, but instead it is
dogging.  I am getting just 2 MB/sec throughput and would expect to be
pushing the network.  Here is the options file I am using:

LANG AMENG
tcpserveraddress fftsm01
changingretries 0
resourceutilization 10
schedlogretention 10
errorlogretention 10
compression yes
txnbytelimit 25600
largecommbuffers yes
tcpnodelay yes
compressalways no
tcpbuffsize 256
tcpwindowsize 50

Any ideas?

Rob Schroeder
Famous Footwear