ADSM-L

Re: [ADSM-L] WAN performance

2016-02-18 14:36:05
Subject: Re: [ADSM-L] WAN performance
From: Tom Alverson <tom.alverson AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 18 Feb 2016 14:33:43 -0500
Looks like 512 is OK in the 7.1 docs:


*IBM Tivoli Storage Manager, Version 7.1*
------------------------------
Tcpbuffsize

The tcpbuffsize option specifies the size of the internal TCP/IP
communication buffer used to transfer data between the client node and
server. Although it uses more memory, a larger buffer can improve
communication performance.
[image: AIX operating systems] [image: HP-UX operating systems] [image:
Linux operating systems] [image: Oracle Solaris operating systems] [image:
Mac OS X operating systems] [image: Windows operating systems] Supported
Clients

This option is valid for all clients.
Options File

[image: AIX operating systems] [image: HP-UX operating systems] [image:
Linux operating systems] [image: Oracle Solaris operating systems] [image:
Mac OS X operating systems] Place this option in the dsm.sys file within a
server stanza. You can set this option on the Communication tab, in the Buffer
Size field in the Preferences editor.

[image: Windows operating systems] Place this option in the client options
file (dsm.opt). You can set this option on the Communication tab, in the Buffer
Size field in the Preferences editor.
Syntax

[image: Read syntax diagram][image: Skip visual syntax diagram]
<http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.client.doc/r_opt_tcpbuffsize.html?lang=en-us#d287668e133>
>>-TCPBuffsize-- --*size*----------------------------------------><


ParameterssizeSpecifies the size, in kilobytes, that you want to use for
the internal TCP/IP communication buffer. The range of values is 1 through
512; the default is 32.

Depending on the operating system communication settings, your system might
not accept all values in the range of 1 through 512.

On Thu, Feb 18, 2016 at 2:15 PM, Skylar Thompson <skylar2 AT u.washington DOT 
edu>
wrote:

> I thought TCPBUFFSIZE could only go up to 64? It could be that setting it
> to 512 actually sets it to the default of 16.
>
> On Thu, Feb 18, 2016 at 02:03:26PM -0500, Tom Alverson wrote:
> > I am seeing very poor WAN performance on all of my (wan based) TSM
> > backups.  Due to the latency (40 msec typical) I normally only get about
> > 20% of the available bandwidth used by a TSM backup.  With EMC Networker
> I
> > get over 90% utilization.  I have already set all of these recommended
> > options:
> >
> > RESOURCEUTILIZATION 2
> >
> > TXNBYTELIMIT 2097152
> >
> > TCPNODELAY YES
> >
> > TCPBUFFSIZE 512
> >
> > TCPWINDOWSIZE 2048
> >
> > LARGECOMMBUFFERS YES
> >
> >
> > Does anyone know of anything else that could help performance?  Has
> anyone
> > used a Riverbed accelerator for TSM backups?
> >
> >
> > Tom
>
> --
> -- Skylar Thompson (skylar2 AT u.washington DOT edu)
> -- Genome Sciences Department, System Administrator
> -- Foege Building S046, (206)-685-7354
> -- University of Washington School of Medicine
>

<Prev in Thread] Current Thread [Next in Thread>