topic Re: Disk Bottlenecks in Operating System - HP-UX

Disk Bottlenecks

Tod Isaacson — Thu, 06 Apr 2000 08:48:37 GMT

I was looking in glance plus at the disk performance. It said our system was
receiving a bunch of disk bottlenecks. Does anyone know what this means and
what I need to do to fix this. Thanks in advance for you help. -Tod

Re: Disk Bottlenecks

Evan Day_1 — Thu, 06 Apr 2000 09:23:06 GMT

Disk bottlenecks happen when there are a lot of read/write requests to the same
physical disk. One way to fix this is to identify the file systems or logical
volumes that are used most often and place them on separate physical disks,
thus spreading the number of reads/writes across multiple disks. You can go
one step further and place them on separate IO channels if performance is still
suffering.

Check IO by File Sys, IO by Disk, and IO by Logl Vol to get an idea of which
filesystems and/or disks are stressed. You can also see which PIDs are the top
disk users.

You may also want to check the Global Waits in glance to see just what
percentage of processes are waiting on Disk I/O. All Glance is really saying
when it warns of a disk bottleneck is that there is a lot of activity on the
disks and you may run into a bottleneck.

-Evan

Re: Disk Bottlenecks

Jeffrey Killian — Tue, 23 May 2000 13:26:42 GMT

Tod,

We are having the same issues here where I work. What I would like to know is your enviroment and what if any ERP systems or Databases. Maybe we could share information..

Re: Disk Bottlenecks

Jeffrey Killian — Tue, 23 May 2000 13:30:19 GMT

Tod,
Sorry here is my email

Dlabonte@ime.net

Re: Disk Bottlenecks

Norm Clary — Tue, 23 May 2000 20:36:43 GMT

If have have sar running you can us the sar -d command to l list the disk drives. This will show you want disk drives are busy. Look at the %busy colum and the avwait and avserv colums. %busy should never be over 50%. And, avwait should not be greater then avserv.

The sar -d data is based on the disk drive, not the file system. You can use Glance to with the (v) option to isolate the problem to a logical volume If the disk having the problem has multiple logical volulmes, moving a busy lv to a new disk should help with disk bottlenecks.

Also, you could add a mirror to the volume group and mirror the offending lvol to the new disk. This will really help with reads, but if the disk bottleneck is mainly caused by writes, this wont really help much.

If you only have one lvol on the busy disk, you could strip the lvol over several disks to help spread the load out.

I hope this gives you some ideas.

Norm Clary