Nothing to see here. As far as I'm concerned, this is a good size; when
MPE/iX reads the disk, it will pick up a number of 4kbyte pages, and each of
these pages will have 4 of these MPE record, 4 IMAGE records. I forget how
many pages MPE picks up at one time,(age and mileage do take their toll,)
but this is ok.
Denys...
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Jim Phillips
Sent: Monday, February 11, 2008 7:25 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] Howmessy
Sorry for the delay...
FO SETS from QUERY:
ITEM CURRENT ENTRY ENTRY BLOCKING
SETS: TYPE COUNT CAPACITY COUNT LENGTH FACTOR
PNM M 117 24859 19385 349 1
LISTF,2:
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
MMSDB101* PRIV 512W FB 24859 24859 1 99440 1 *
Let the fray continue.....
Jim
Denys Beauchemin <[log in to unmask]> wrote:
Before you change the capacity, could you at least tell us the size of the
IMAGE record and maybe show a listf,2 of the dataset in question? I don't
like a BF of 1 unless it's a big record.
Denys...
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Jim Phillips
Sent: Friday, February 08, 2008 1:45 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Howmessy
Thanks for the reply, Gilles. Patrick from Adager replied as well and after
speaking to him on the phone, I am convinced that a capacity change is in
order.
Jim
Gilles Schipper wrote:
I'd try to reduce that max.blocks by increasing the capacity. Try
increasing to 32001 and run hm again to see the effect on max.blocks.
At 01:20 PM 2008-02-08, Jim Phillips wrote:
>So, I ran Howmessy on the main data base here and the very first
>data set looks very suspicious. The report for this manual master
>shows 78% full (19381 entries, 24859 capacity), 30.3% secondaries,
>maximum blocks=190, blocking factor=1, maximum chain=7, average
>chain=1.43, standard deviation=.70, expanded blocks=1.43, average
>blocks=2.30, elongation=1.60 and, are you ready for this,
>inefficient pointers=100%!
>
> My first thought was to increase the blocking factor (my thinking
> is with a blocking factor of 1, every pointer must cross a block
> boundary). I could also increase the capacity somewhat to get the
> load factor down to 70% or so.
>
> What does this august group recommend?
>
> Jim
>
>
>---------------------------------
>Looking for last minute shopping deals? Find them fast with Yahoo! Search.
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
>
>--
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.5.516 / Virus Database: 269.19.21/1265 - Release Date:
>2008-02-07 11:17 AM
----------------------------------------------------------------------------
---------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651 Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000 Fax: 905.889.3001
email: [log in to unmask] web: http://www.gsainc.com
----------------------------------------------------------------------------
---------------------
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
---------------------------------
Never miss a thing. Make Yahoo your homepage.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
