This document describes the settings for intra- and inter-physical volume allocation policies to better organize logical volumes for increased I/O performance. It also provides information on configuring the system for highest performance or highest availability when creating logical volumes.
This document applies to AIX Version 3.2.
To change the intra policy, use the chlv command as follows:
chlv -a {m c e ie im} LVname
Logical volumes with the most active I/O should be placed in the center, while inactive ones should reside on the edges. The logical volume might be split across the different edges when allocated. Since it is assumed that the disk heads generally linger in the center of the disk, it would take equal time for the heads to move to the edges to capture data from the least active LVs. This would only impact performance if the data on the edges is read frequently or in large blocks.
To change the inter policy, use the chlv command as follows:
chlv -e {x m} LVnamewhere x = maximum and m = minimum allocation policy.
After the policies have been set for all logical volumes involved, the LVs may be reorganized by using the reorgvg command. This command will reorganize all physical partitions to match the allocation policies assigned to each LV. Since the system cannot always fill all of the requirements, it will put the LVs as close as possible to the positions specified. Enter:
reorgvg VGname LVname1 LVname2 ...
VGname is the name of the volume group in which the LVs are contained, and LVname1, LVname2, etc are the names of the logical volumes to be reorganized. The order of the LVnames indicates the precedence of the organization of the LVs. The first one in the list will get the highest consideration in its allocation position. If you do not list any LVnames, then all LVs will be reorganized. In this case, the precedence will simply be determined by the order in which the LVs were originally created.
In general, whenever LVM is configured to provide better performance, the availability of the system is impacted.
To configure the system for the highest performance, follow these guidelines when creating logical volumes:
Scheduling Policy PARALLEL Allocate each logical partition copy on a separate disk? YES
The parallel-write scheduling policy starts the write operation for all the physical partitions in a logical partition at the same time. When the write operation to the physical partition that takes longest to complete finishes, the write operation returns.
The YES in the allocation policy sets the STRICT variable in the mklv command run by SMIT. This setting ensures that no two copies of a logical volume partition will reside on the same physical volume if it can be avoided.
This will spread each logical volume across as many physical volumes as possible, thereby allowing the work of reading or writing to a logical volume to be shared among several physical volumes.
To configure the system for the highest availability, follow these guidelines when creating logical volumes:
Also consider the following, which may increase system availability:
To determine the physical partition fragmentation on a disk, such as hdisk0, issue the command:
lspv -l hdisk0This command will list the logical volumes that are on that disk, the number of physical partitions from that logical volume that are on that disk, and how those physical partitions are distributed on the disk. Under DISTRIBUTION the number of physical partitions in the outer edge, outer middle, center, inner middle, and inner edge sections of the disk are listed.
To view the actual order of physical partitions on the disk, use the lspv -M hdisk0 command. The logical volumes that are on the fragmented portions of the disk will display. The numbers shown in the output are the physical partition number on the disk (physical volume) and the physical partition number on the logical volume.
If a logical volume is on fragmented portions of a disk, reorganize your disk. Place the logical volumes with the highest I/O nearest to the center of the disk.
Although it is possible to check the fragmentation of physical partitions, the fragmentation of the actual data within a file system cannot be checked. This fragmentation is caused by continual creation and removal of files. If performance has degraded over a period of time, then it is quite possible that there is fragmentation within your file system.
The only way to alleviate this type of fragmentation is to backup the file
system by file name, delete the file system, recreate the file system with
the mkfs command, and then restore the file system data.
[ Doc Ref: 90605201014634 Publish Date: Oct. 16, 2000 4FAX Ref: 9300 ]