You measure with what you have. System crashes. If you set something to small or to large then the system crashes or runs poorly. Change it until it runs right. You don't need tools from velocity or others to tell you what to adjust. They are only needed if you want the system to stay up while you are tuning it. Obviously your management has accepted the cost of the system crashes as the price of tuning the system. Some companies management think that the price of the velocity tools is less than the price of crashes. Yours doesn't so give them what they want.
[EMAIL PROTECTED] wrote:
I'd love to measure. The question is measuring what. Since I don't have the tools, won't be getting the tools, I have to find other means to understand what a single instance of IHS is using resource wise. If anyone has any idea on HOW to do that without such things as the fine products from velocity, I'd love to know. Sigh. I'm amazed we've done what we've done given the level of support we actually get.
-- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
