In the first place, drop the compression.  Compression is only intended for
slow links where the amount of data sent over the wire is impotant.  It is a
huge CPU burden for the client to compress the data, so high transfer rates
are not possible with it enabled.

Personaly I would say that any line above 2Mbits/s should not use compression.

Just MHO,

Thorhallur


On Fri, Sep 28, 2001 at 02:33:27PM -0500, Rob Schroeder wrote:
> 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