HP's philosophy is to design balanced systems in which no single component becomes a performancebottleneck. HP has made significant enhancements to I/O performance in order to keep pace with the speed of our CPUs. I/O performance depends on several parts of the system working together efficiently. The I/Osubsystems have been redesigned so that they now offer the industry's fastest and most functional I/O asstandard equipment.To improve disk I/O performance:
Distribute the work load across multiple disks.
Disk I/O performance can be improved by splitting the work load. In many configurations, a single drive must handle operating system access, swap, and data file accesssimultaneously. If these different tasks can be distributed across multiple disks then the job can be shared,providing subsequent performance improvements. For example, a system might be configured with fourlogical volumes, spread accross more than one physical volume. The HP−UX operating system could exist onone volume, the application on a second volume, swap space interleaved across all local disk drives and datafiles on a fourth volume.
Split swap space across two or more disk volumes.
Device swap space can be distributed across disk volumesand interleaved. This will improve performance if your system starts paging. This is discussed in more detailin the section on Swap Space Configuration later in this document.
Enable Asynchronous I/O
− By default, HP−UX uses synchronous disk I/O, when writing file system "metastructures" (super block, directory blocks, inodes, etc.) to disk. This means that any file system activity of thistype must complete to the disk before the program is allowed to continue; the process does not regain controluntil completion of the physical I/O. When HP−UX writes to disk asynchronously, I/O is scheduled at somelater time and the process regains control immediately, without waiting.Synchronous writes of the meta structures ensure file system integrity in case of system crash, but this kind of disk writing also impedes system performance. Run−time performance increases significantly (up to roughlyten percent) on I/O intensive applications when all disk writes occur asynchronously; little effect is seen forcompute−bound processes. Benchmarks have shown that load times for large files can be improved by asmuch as 20% using asynchronous I/O. However, if a system using asynchronous disk writes of metastructures crashes, recovery might require system administrator intervention using fsck and, might also causedata loss. You must determine whether the improved performance is worth the slight risk of data loss in theevent of a system crash. A UPS device, used in a power failure event will help reduce the risk of lost data.Asynchronous writing of the file system meta structures is enabled by setting the value of the kernelparameter fs_async to 1 and disabled by setting it to 0, the default. For instructions on how to configure kernelparameters, see the section Kernel Configuration Parameters later in this document.You may want to use a RAID (Redundant Array of Inexpensive Disks) configuration for reliability. MostRAID configurations do not perform as well as non−RAID configurations, but the reliability gains may beworth it.
Graphics and Color Mapping
Many tools use 2−D graphics, and are X11 based. Thus, a platform's X11 performance is key to maximizingthe graphics performance of these applications. This can be measured with the standard benchmark xmark93.
HP Global Technical Partner − CadenceDisk3