Disk utilization

[Kourla]

Hi,

We are running an application on HP-UX L3000 server. The disk layout is explained below.
Three 36.4GB hardidsks.

First disk used for the oracle indexes and root partition (18.2 GB each)

Second disk is used for oracle tables and Application logs. (18.2 GB each)

Third disk is used for Oracle logs (18.2 GB) and remaining 18.2 GB is free in the third disk.

On the second disk almost the disk IO rate is 100% always, is anybody have any idea why this is always 100% do we have to tune any kernal parameters.
Presently we are trying to test with following options

1. Moving the Application logs from second disk to 3 disk. (i.e. in third disk we have 18.2 GB free space, we are planning to create another lvol in the volume group of third disk and move all the logs from disk 2 lvol to newly created lvol)

2. Adding separate disk for application logs and moving all the logs data from second disk to new disk.

Is any options mentioned above will solve the disk I/O problem? or is there any body have any ideas please..

[T G Manikandan]

yes,you are right.

The Disk is going 100% as the Oracle processes go on writing with the logfiles and the datafiles.

Distribution the datafiles and logfiles should improve the situation.


I do not think any kernel parameter can help you on this.

If you have Glance then you can get a clear picture on the process which has a high I/O rate on the disk.


Thanks

[Michael Tully]

Whilst you only have three disks you will have stacks of Disk IO. Your best bet is to add as many disks as possible to even out the load, particularly for logging. Moving some of the load from disk 2 to 3 will only be a temporary solution.

[George Petrides_1]

Adding more disks and STRIPING will take care of your problem. When you stripe you evenly distribute the I/O to multiple disks hence multiple mechanical devices and you can see signigicant performance increase.
George

[Dave Wherry]

You are limited in what you can do with only 3 disks. As others have already said, your first step should be to get more disks and more evenly distribute the load. I always have my operating system and only the operating system in volume group 0 (vg00). Then create additional volume groups on other disks for the applications and data. And, use striping.
Having said all that, if you can not get additional disks for this system and keep everything in 1 volume group, I would use Ignite and rebuild the system. Create a make_tape_recovery tape and rebuild from that striping all of your logical volumes across the 3 disks.
In an Oracle environment it can be difficult to pinpoint where the majority of your activity will be. If it is for the most part static data and mostly reads happening, there will not be much activity in your logs. So putting the logs on a seperate disk means that disk will not be busy but, your data disk(s) may be overworked.
If a lot of data is being added and or deleted, the data and log volumes will be active.
If you have inadequate memory you may be swapping so the swap devices can be very active.
With only 3 disks I would stripe across all of them and hope it all balances out somewhat. More disks is really the answer.

[Rizwan Mohammed]

Hi

for this issue ,if you have free memory u can change some kernel parmeter to increase the i/o performance
nbuff 5
dbcmax 25
dbcmin 5

this will give some performanc enchanment ,as it copies more data to memory ,so it doesnt aceess disk quite frequently

Rizwan

[Bill Hassell]

There's nothing you can do to really improve anything in the kernel. There are several distinct categories of files in Oracle and each category should have a separate hpysical disk (separate lvols on the same disk will do nothing). The Oracle data areas are randomly accessed and should be on a separate disk (or disks). Archive/rollback logs are intense serial activities and must be on a separate disk.

Striping might help a bit but you just don't have enough disks to make much of a difference.

[Steven E. Protter]

Oracle does not recommend striping for optimal performance.

Though it can help you out in your currenet situation, you'll get better performance using Raid 1/0 mirroring.

lvextend -m 1 /dev/vg01/oradata /dev/dsk/c#t#d#

The archive logs and such don't benefit as much from this setup.

Striping will improve reliability, especially if you strip across more disks, but there is a disk performance penalty.

SEP