Michael Wanzong wrote:
 
 
>     Hi,
>
>     We are currently experiencing some system performance problems.  As
>     near as we can tell, part of the problem may be that we have 3 of 6
>     RAID drives in our proudction volume set running at 100% utilization
 
!!! Not good...
 
>     for most of the day (according to GlanceXL).  The other 3 RAID's are
>     running around 35%.  I would like to try to find out two things:
>
>        1)  List of files on each ldev.  (I know I can parse this out of
>     LISTF,3 but I don't have time to write a program for this.  I also
>     don't own MPEX).
 
Try a demo of De-Frag/X, from Lund Performance Solutions (541)926-3800.  It
has the capability of analyzing each ldev, and can display files on each ldev.
 
>
>        2)  Some statistics on number of I/O's per file on each LDEV over a
>     period of time.  We have SCOPE/XL with Laser/RX and Perf/RX, but can't
>     seem to wrestle this information out of these.
>
Unfortunately, there is no longer any system-wide reliable way of getting an
accurate count of i/o's per file.  In the old days you could enable FILE
CLOSE in the system log files and generate a report with the contributed
FILERPT program.  Nowadays, much of the i/o on a system isn't logged
anywhere (due to the way mapped file access is handled outside of the file
system).  The best thing you can do is guess based on your knowledge of the
application.  Sorry about that.
 
 
>     Bottom line:  I want to find out which files to move off the heavy use
>     LDEV's to spread the load.  Also, a utilty to move the files (PRIV)
>     would be handy!
>
 
This can often be a lot of work but can be worth it.  A friend of mine once
went to the trouble of the following:
 
1.  Run FILERPT to determine list of most heavily hit files
2.  Convert FILERPT output to a STORE !indirect file
3.  STORE heavily hit files followed by all other files on system
4.  Perform system install/reload (depending on O.S.)
5.  Perform RESTORE, whereby all heavily hit files are RESTORE'd first,
guaranteeing that the most heavily hit files are clumped on the (logically)
outer edges of the disk platters.
 
Seems like a lot of work (since it is) but isn't really possible any longer
due to the reasons stated above.
 
What I suggest instead is that you defragment/fragment important disk files,
as indicated by the most typical access methodology used to gain access to
the file, and condense each disk drive.  You can do these functions with
De-Frag/X, which Stan Sieler and I designed, and he wrote.
 
BTW, I don't gain (any longer!) from these recommendations so I don't feel
particularly needful of (PLUG,/PLUG) warnings.
 
>     Does anyone have any suggestions?  Is there anything in MPE that can
>     help?  The CSL?  A feature we are missing in Glance or Perf or Laser?
>
 
Glance/Perfview/Laser RX don't really address this issue very well.
However, VOLUTIL has the beginnings of something which you can get started
with.  It has the CONTIGVOL command, for which there has been extensive
dialogue amongst this list in the past.  See the archives or email me directly.
 
>     System Specs:
>        HP3000 996/800 w/ 2 Gigs Memory
>        MPE 5.0 Express 2
>
>     TIA!!
>
>     Mike Wanzong
>     [log in to unmask]
>
>
 
Bill
---
Bill Lancaster
Lancaster Consulting
(541)926-1542 (phone)
(541)917-0807 (fax)
[log in to unmask]
http://www.proaxis.com/~bill