On 11-04-21 07:55 AM, Doug Weimer wrote:
> Many comments in the 'amount of swap' thread mentioned the importance of
> understanding a system's workload. This is something that I often
> struggle with. What tools and techniques do you use to better understand
> the expected workload for a system? Tools like top, iostat, and vmstat
> give a picture of a systems current state. How do you take the next step
> to understand why the system is in it's current state and what
> changes/upgrades would alleviate the problem?
>

I'm still quite fond of Orca. The only one I find that is much better is the 
HP one (used to be OpenView, not sure what the current trendy name is). It 
costs a few arms and legs but is way ahead of everything else I've seen. 
Pareto is your friend (use a free orca/cacti/sar like tool on most machines, 
spend the money on the very few where you really need the granularity and the 
level of details you get from a commercial product).

-- 
Yves.                                                  http://www.SollerS.ca/
                                                        http://blog.zioup.org/
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to