*** Original Author: ADSM-L @ MARIST - ** Remote User **; 03/17/98 05:53pm
>Received: from VM.MARIST.EDU by AUDUCADM.DUC.AUBURN.EDU (IBM MVS SMTP V3R1)
> with TCP; Tue, 17 Mar 98 17:53:20 CST
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R3)
> with BSMTP id 3025; Tue, 17 Mar 98 18:17:02 EST
>Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
> (LMail V1.2b/1.8b) with BSMTP id 2865; Tue, 17 Mar 1998 18:17:01 -0500
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (LISTSERV release 1.8c) with NJE
> id 0163 for ADSM-L AT VM.MARIST DOT EDU; Tue, 17 Mar 1998 18:16:59
> -0500
>Received: from MARIST (NJE origin SMTP@MARIST) by VM.MARIST.EDU (LMail
> V1.2b/1.8b) with BSMTP id 2853; Tue, 17 Mar 1998 18:16:58 -0500
>Received: from louitr1.humana.com by VM.MARIST.EDU (IBM VM SMTP V2R3) with TCP;
> Tue, 17 Mar 98 18:16:57 EST
>Received: from inweb_dmz.humana.com by louitr1.humana.com via smtpd (for
> vm.marist.edu 148.100.1.2 ) with SMTP; 17 Mar 1998 23:17:32 UT
>Received: from LOUDOM2 by louita1.humana.com via smtpd (for vm.marist.edu
> 148.100.1.2 ) with SMTP; 17 Mar 1998 23:15:41 UT
>Received: by loudom2.humana.com(Lotus SMTP MTA v1.1 (385.6 5-6-1997)) id
> 852565CA.007F8F92 ; Tue, 17 Mar 1998 18:13:18 -0500
>X-Lotus-FromDomain: HUMANA
>Mime-Version: 1.0
>Content-type: text/plain; charset=US-ASCII
>Message-ID: <862565CA.007E84FF.00 AT loudom2.humana DOT com>
>Date: Tue, 17 Mar 1998 17:15:38 -0600
>Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>Sender: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>From: Julie Phinney <jphinney AT HUMANA DOT COM>
>Subject: ADSM V3 tuning on MVS
>To: ADSM-L AT VM.MARIST DOT EDU
>
I am moving ADSM on OS/390 from V2 to V3. In reviewing the server options
file, I noticed a couple parms that I tuned before, according to a
Performance and Tuning Guide for ADSM, that may need revisiting now with
ADSM V3 and it's small file aggregation.
The numbers I have specified are:
TXNGROUPMAX 40 (I seem to remember some problem, a long time ago, when
I tried hiking that number to the max)
Movebatchsize 1000 (can't remember why I did that, the doc in the opt
file says that number can only be as high as 256)
Movesizethresh 500
Are you all moving that TXNGROUPMAX up to something higher when you go to
V3, to get more performance benefit from small file aggregation?
What are you V3 users on OS/390 using for those 3 numbers?
Does anyone know if there is a new, updated Performance and Tuning Guide
for ADSM for V3?
Thanks,
Julie
*** Comments From: STEWAJM - Stewart, Mike; 03/18/98 08:46am
I moved from the V2.1 to V3.1 on OS/390 this past weekend.
I have:
TXNGroupmax 256 (increased from 100 on V2)
MOVEBatchsize 1000
MOVESizethresh 500
I think I remember setting the Movebatchsize to 1000 and
TXNgroupmax to 256 based on an IBM recommendation at
some point.
So far the only problem I've run into is that I
had my options stored in a partiioned dataset, and
as soon as I tried using the admin client to update
the client options the server 0C4'ed and went down.
The server doesn't support updating the options in a PDS
member.
However, just because I haven't had alot of problems doesn't
mean I'm particularly happy with V3. The benefits I was
hoping to see aren't there. Multiprocessing didn't make it
in. ODBC access seems to be very finicky. And it is
_much_ more expensive than V2 if you have alot of clients.
(I'm suprised I haven't heard much complaining about the
increase in cost.)
In fact, the cost has me looking at NT servers, which is
why I was wondering what the capacity of an NT server was,
and wondered if I could get some samples from those of you
running the NT version of the server.
|
