You should get quite a bit more than this level of performance. To be
certain, you need to find where the bottleneck is. But, you might try
the following:

a) Look at your "no" values for TCP on the AIX box. You want

        sb_max=1310720
        tcp_sendspace=65536 (or bigger)
        tcp_recvspace=65536 (or bigger)
        rfc1323=1
        ipqmaxlen=50

        Do the equivalent for your clients.

b) Use vmtune increase AIX read ahead on the server:

        vmtune -R 64 -F184 -c 1

C) Make sure ADSM Server has
        txngroupmax 256
        movebatchsize 1000
        movesizethresh 500

Client should have
        txnbytelimit 25600
        tcpbuffsize 32

Also make sure your cache is has 98%+ hit ratio.   Compression should be
"off" on the clients, for best performance on your "fast" Ethernet.

> -----Original Message-----
> From: Simon Watson
> [SMTP:Simon.S.Watson AT OPENMAIL.FIC32.BSPSER.SIMIS DOT COM]
> Sent: Thursday, May 14, 1998 02:09 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Server Performance
>
> We are a fairly new ADSM site, yet to go into production.
>
> AIX 4.2.1
> ADSM 3.1.0.2 (soon to be 3.1.1.2 when I can successfully download it!)
> AIX, HP UX, WNT 4 clients
> 3494 with 2 3590 drives
> 10BaseT and 100BaseT Clients (Server is on 100BAseT)
> Disk pool as first pool and migrated then to tape daily.
>
> We have been doing some backup and restore tests over 100BAseT and to
> date performance is dissapointing.
>
> Typical Network Data transfer rates are 4MB/sec although Aggregate
> Data
> transfer rates are only .4MB/sec, ie 1/10th the network rate.  Neither
> the server or the client are particularly busy during the transfers.
> This is similar for backup (direct to disk) and restores (from tape).
> This translates to almost 1.5 GB/hour throughput which is a bit poor.
> I was expecting more than 10 times this figure.
>
> The network seems OK as Network Data transfer rate is reasonable and
> similar to an FTP.
>
> IBM has installed the server for us and has the following parameters
> set
>
> Server:  TCPWindow   0
>         TCPNOdelay    Yes
>
> Client:  No specific settings in dsm.sys or dsm.opt
>
> I am not sure what 0 means, documentation only refers to this value
> for NT.
>
> I would expect that setting the TCPWindowsize on server & client (in
> dsm.sys I presume) to a larger value ie 2048, which is the maximum
> would improve performance and also setting TCPNOdelay to NO would also
> help.
>
> Should I do this?
>
> Any other suggestions?
>
> Regards,
> Simon