|
Dave, We stopped having space concerns a while ago; a couple of model upgrades ago I included a bunch of DASD to get the ASP down in the <35% range. But I didn't buy the disks for the space. I bought them to get the arm utilization down to something reasonable. I would suggest that you examine the disk arm utilization / percent busy to see if your disks are thrashing. If their % busy is high (IIRC above 40% for internal disks), there is a performance bottleneck that's causing the CPU to potentially sit idle while waiting for disk I/Os to complete. I would use that as part of an argument for additional and/or faster arms. But if you can't buy more DASD and have to continue to clean up the system: 1. Run a RTVDSKINF periodically and then PRTDSKINF to examine the results. I run them weekly here. You may find objects that haven't been used for months and be able to present a good argument from that for archiving those items to tape. 2. If the developers do need their test data, I would question just how much they need. Perhaps their test files, which may be copies of production data, can be pared down by deleting 90% of their contents. Followed by a reorg and you might reclaim even more space. This should still leave sufficient data for most testing activities. HTH, John -----Original Message----- From: Dave Snyder [mailto:dsnyder@xxxxxxxxxx] Sent: Thursday, March 06, 2003 11:58 AM To: midrange-l@xxxxxxxxxxxx Subject: Critical disk usage amount I am trying to convince people here that we need to add more disk to our AS400. We currently have 256GIG and are at 74% utilization. What common usage percentage do people use as a threshold that, if we go beyond this percentage, there will be issues? We have cleared off as much as possible but people constantly want more test information left on the box, so we continue to grow every month. Thanks for the thoughts. Dave _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.