|
HP OpenVMS Systemsask the wizard |
|
The Question is: Our clients is in the process of migrating to a GS1280 machine utilising HP EVA storage (EVA 5000). We have noticed when tuning RMS files on the existing (EMC) storage that indexed RMS files that are processed from end-to-end in large batch jobs take less time to process when the bucket size is increased by dramatically more than the edit/fdl procedure recommends. My question is as follows: Are there any recommended tuning guidelines for RMS files on HP EVA storage? Can the edit/fdl/nointeractive procedure be used to give a larger bucket size (the EMPHASIS=FLATTER_FILES doesn't seem to make much difference). We need this as we need to have an automated way of regularly tuning our hundreds of RMS files -- which makes using the manual interactive way of using edit/fdl impractical. Any advice welcome! The Answer is : Tuning to a specific device is not generally an appropriate nor an expeditious course, nor are there generally any performance-tuning guidelines made available for particular devices. Rather, the recommendation is to tune the application for maximal performance within the current target environment -- systematically find and remove the performance bottlenecks. With systems of the scale of the AlphaServer GS1280 series, the OpenVMS Wizard would also enlist the assistance of the HP Customer Services organization. If you are having to regularly tune your RMS files, then you are performing a comparatively unexpected task -- applications do not normally change behaviour in this fashion, and do not normally require frequent retuning. More commonly, the use of FDL files (as created from EDIT/FDL or ANALYZE/RMS/FDL) and the occasional use of the CONVERT/FDL command (as required) would be expected. You can also choose to use available callable APIs, including the fdl$create routine and the conv$ callable support. For files that are (re)created regularly, use of the CREATE/FDL command or of the fdl$create call can provide an easy way to tailor and to customize the file creation operations. Other tuning considerations include the necessary step of application profiling -- find the bottleneck(s) -- and evaluation of such other considerations such as available system resources, device performance, contention, process quotas, and such. For generic programming information, please see topic (1661). Other system, application, and RMS file tuning discussions include (292), (1676), (2259), (2618), (2764), (2794), (3345), (3598), (3948), (4341), (4365), (6149), (6718), (6886), (7425), (7557), (7757), (8409), (9020) and (9932). Other tuning-related discussions are also available. For information on FDL, the DCL commands cited, fdl$create, and the conv$ support, please see the OpenvMS documentation.
|