A dataspace should be faster; Vdisks mean that CMS is doing virItual l/O that CP later must handle. Dataspaces is just moving data around, no CMS I/O routines, nor CP overhead. But, maybe you mean CMS files in SFS dataspaces. And even then I guess SFS dataspaces are faster than VDISKs: CP won't be involved if the access density is hgih enough to keep the data resident. Each VDISK access involves CP the residence of the vdisk data doesn't change that.
Kris, IBM Belgium, VM customer support "Schuh, Richard" <[EMAIL PROTECTED]> Sent by: VM/ESA and z/VM Discussions <[email protected]> 2005-11-18 17:31 Please respond to VM/ESA and z/VM Discussions To [email protected] cc Subject V-disk vs. Data Space Has anyone compared the relative performance of shared V-disk and Data Spaces for R/O data? We have a project that is going to have a lot of data in files of various sizes that will be read by about 20 different machines that will all be logged on at the same time. This data is to be fed to another machine, not a guest, with the intent of testing its bounds. We want to insure as much as possible that VM will not be the bottleneck when we run into one. Thanks, Richard Schuh
