Adding the 60,001st entry took the 500 CPU seconds.  We loaded the
first 60,000 duplicates in a batch job, with FCOPY, so I don't know
where it started slowing down.

----------
> From: Mark Landin <[log in to unmask]>
> >
> >We were recently doing some testing of a KSAM/CM file with over
60,000
> >duplicate keys, and thought of KSAM/xl as a possible solution to
the
> >poor performance we were seeing. Adding a new duplicate key to
KSAM/CM
> >was taking about 40 CPU seconds, but KSAM/xl took over 500 CPU
> >seconds!
>
> Are you saying it took 500 CPU seconds to add all 60,000 keys, to
add each key,
> or to add the 60,000th key? If the last, how long did it take to add
the
> 30,000th key? or the 5,000th key? At what point did the XL
performance become
> WORSE than the CM performance?
>