You can use 'onstat -g iof' to see where the database is writing to, and
then take the appropriate steps (move table/dbspaces, add spindles, ...) to
correct any bottlenecks.
iostat and vmstat are useful, but all they tell you is that a process is
being piggy. You need to go to the next layer to see how to distribute the
database for maximum efficiency. The combination of both steps is usually
pretty good justification for additional hardware ;)
SC
> I'm wondering how many of you out there use iostat?
> Yes, I know that it is not an informix command, but that it is a AIX
> command.
> I use it to determine io contention on my hard drives, this helps me to
> determine,
> if I need to move my growing tables to new dbspaces on different
> harddrives