Are either of the detail paths sorted?  That would cause it - you could spped it up by sorting your flat input file first.

My personal belief is that if your average chain lengths get to be very long (7 or more, say...) then use an IMSAM key if you need sorted retrieval.

-Dave





[log in to unmask] on 12/26/2001 09:14:00 AM
To:     [log in to unmask]@Internet
cc:      (bcc: David T Darnell/CO/KAIPERM)
Subject:        [HP3000-L] Slowing down

I have a IMAGE data set with 2 masters.
The detail had 135,000,000 and a capacity of 185,000,000 when I started.  I
 turned off the TPI (OMNIDEX) transaction manager.

Then I use Adager to expand the capacity of the detail set to 213,000,000.

The 2 masters I expanded to  30% full.

I am using SUPRTOOL, OPEN the base MODE 3.

PUT with SET DEFER ON.

I have 2 files to load 37 million and 27 million.

On my test of the first 5 million records I got 5,200 puts per min., which is
 what I got in the first 5 million records.  I am at 8 million records now.  I
 am getting about 2000 puts per min.

Any Idea's why I am slowing down.

I guess that the number of master records associated with the number of detail
 is causing long chain length.  Which would cause the CPU a lot of work.

Box is 937SX 5.5 PP6


Kent Wallace
Boise Id.

* 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 *