I don't think hashing is an issue, since Carl said these are details, with
no paths, but I wonder whether these datasets were erased (or packed) after
extracting the records.  If Image is traversing a big delete chain to put
the records, it could be jumping all over the place.

-----Original Message-----
From: Noel Demos [mailto:[log in to unmask]]
Sent: Monday, November 01, 1999 1:12 PM
To: [log in to unmask]
Subject: Re: Performance question


Carl McNamee wrote:
>
> We ran into a unique situation this weekend while testing some batch jobs
> that will be used to perform a database conversion next weekend and I
would
> like to see what the gurus of the list think could be causing us grief.
>
> We have 24 databases split between 6 volume sets.  We are extracting the
> data from then into flat files that reside on 8 different volume sets.  So
> far the process worked very smoothly.
>
Carl, you did not say what you are converting.  If it was a key field,
you may
be impacted by seek time, because the keys are being hashed to different
locations.

Nick D.