Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

direct io size

eran_6
Advisor

direct io size

We have two EMC boxes: Symmetrix & DMX. During performance test for two identical defined disks in two diffrent boxes DECPS return for reading/writing same files diffrent d_io_size:
for Symmetrix - 128 pages and for DMX - 64 pages.
OVMS 7.3-1. There is XFC, but files set "no_cache".
The test done by simple copy command from the same process.

What may be a reason for this diffrence?
5 REPLIES
Antoniov.
Honored Contributor

Re: direct io size

Hello visa,
when you write 128 pages or 64 pages do you want say blocks?
Do you see allocated block or used blocks?
If you see allocated block may be different cluster size between two disk.
Type SHO DEV /FUL and look at details of disk. Also use DIR/FULL to see allocated and use blocks.

H.T.H.
Antoniov
Antonio Maria Vigliotti
eran_6
Advisor

Re: direct io size

1. Pages in DecPS are same blocks

2. Was written the disks definition the same,
so cluster size is 362 for both.

Thanks
Willem Grooters
Honored Contributor

Re: direct io size

Just a few hints:
* The boxes will no doubt have their own controllers - which can have a difference in handling the chuncks of data.
* Each box will have it's own cache - out of VMS's control. "no_cache" is strictly VMS-bound so that would not influence the EMC boxes. Handling of these caches is the boxes' concern. Since these are different, there might be a difference in handling
* If the path to one box passes other type of hardware (FC switches) than the other, this may cause a difference in pagesize, simply because the ability of this different hardware to handle the datastream.
* If the hardware underway is the same, but still different, it could (my guess) be possible that configuration could be part of the problem. Probably even if path to each box is parallel using the same switches, there could be a difference in confuration casuing this difference.
Willem Grooters
OpenVMS Developer & System Manager
Amit Levin
Occasional Advisor

Re: direct io size

You may want to check which is the source disk of the copy operation.
if you are coping sym ---> sym that might
explain your results because data may stil
be in cache.
computers is the name and coding is the game, dont play the game, just say the name
eran_6
Advisor

Re: direct io size

Hi Amit! Thanks.
1. Test copy for reading was from disk to nl:
2. Would you explain the mechanism for setting direct io size? Where may be place of sym caching for it?