>we made a move data of a dirmc copy pool. The move data process
>needs 5:12 hours to move 70 823 172 bytes. Most of the data is read
>from a disk storage pool. For database files we can move up to 10 GB
>per hour.
>
>How can we speed up the move data process for the dirmc pool?
Norbert - A dirmc storage pool is inherently a high overhead area to
deal with because the objects are small. You can only
tune your database and storage pool work unit sizes per the
server BUFPoolsize, MOVEBatchsize, MOVESizethresh, and TCPBufsize
options. And never skimp on server real memory - the single biggest
affector in server performance in modern CPU systems.
Consider also that dirmc isn't what it once was. ADSMv3
introduced the concept of Restore Order. See that entry in
http://people.bu.edu/rbs/ADSM.QuickFacts, or APAR IC24321.
Richard Sims, BU
