Date:     June 2, 1997             Time: 2:28 PM
From:     Jerry Lawson, Specialist
          The Hartford Insurance Group
          (860) 547-2960
------------------------------------------------------
Another TCP/IP 3.2 question...
Another TCP/IP 3.2 question...

Based on the concerns issued here about TCP/IP 3.2, and it's impending
installation on our MVS systems where ADSM runs, we ran a quick benchmark.
On our existing ADSM system, with TCP/IP 3.1, when I run backups from my PC,
A typical session gets a 3,000KB/Sec throughput.  (This is through a 10 MB
Ethernet link).  When I run the same backup from the same PC to an ADSM test
system on the TCP/IP 3.2 system, I average maybe 70KB/sec.  (measured from
the ADSM GUI backup panel.)  MVS performance settings seem to be similar -the
test system used to be our production system, and still has the performance
settings for ADSM there (perf. Group, etc.)

ADSM is at the same level on both systems.  TCP/IP is at a base level of
9702, with additional maintenance on top of that (including the three PTFs
that were listed here within the last week or so.

We have not even tried a restore yet..

I looked in the Accounting section of the Node definition, and it said that
for the test system, I was in a Comm wait 57% of the time.  On the product
system, I was in a Comm wait 20% of the time.

Any suggestions on how to isolate where we are hitting the bottleneck?  Are
there any more known performance problems with TCP/IP 3.2 that sound similar
to this that anyone has seen?

--------------------------------------------------------
                                         Jerry
                                         Jerry

Insanity is doing the same thing over and over..and expecting the results to
be different - Anon.