[ale] Collectl and other peformance tools

[Jim Kinney]

http://download.fedora.redhat.com/pub/epel/5/x86_64/repoview/atop.html

EPEL repo

On Fri, Oct 8, 2010 at 1:07 PM, Lightner, Jeff <jlightner at water.com> wrote:

>   What RHEL repo did you find this in?  It doesn’t seem to be in the
> standard RHEL5 or CentOS5 repos.
>
>
>  ------------------------------
>
> *From:* ale-bounces at ale.org [mailto:ale-bounces at ale.org] *On Behalf Of *Jim
> Kinney
> *Sent:* Friday, October 08, 2010 9:36 AM
>
> *To:* Atlanta Linux Enthusiasts - Yes! We run Linux!
> *Subject:* Re: [ale] Collectl and other peformance tools
>
>
>
> the per-process statistics of atop are exactly the detail level I'm looking
> for. Many thanks! It's not a default installed package with RHEL/Fedora but
> it's in the repos.
>
> On Thu, Oct 7, 2010 at 8:49 PM, Brian Pitts <brian at polibyte.com> wrote:
>
> On 10/07/2010 05:44 PM, Brian Pitts wrote:
> > Atop will change your life.
> >
> > https://lwn.net/Articles/387202/
> >
>
> Sorry for the top post earlier, I'm not used to sending email from my
> phone. I wanted to take a minute to follow up and further tout the
> virtues of atop.
>
> When your performance monitoring system (be it collectd, xymon, opennms,
> or whatever) tells you there's a problem with a server, atop is what you
> want to use when you log in to find the problem. It has completely
> displaced my use of the sysstat suite of tools. It presents all the
> information you could get from sar and pidstat from within the friendly
> interface of top. You can view cpu, memory, i/o, and network statistics
> at the system and per-process level. You can do this in real time or you
> can step through samples recorded earlier. The next time a user
> complains about how things were "slow" the day before, you'll be able to
> go back and pinpoint exactly what was happening. Although the
> interactive interface is what really shines, if you still need sar style
> reports there's atopsar.
>
> The lwn article I linked to earlier is a great overview of what you can
> do with atop. For a more limited but in depth example of using atop this
> paper [0] is good. It's also worth reading because the beginning is a
> good refresher on virtual memory and the end presents a good use case
> for cgroups.
>
> [0] http://www.atoptool.nl/download/case_leakage.pdf
>
> --
> All the best,
> Brian Pitts
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>
>
>
> --
> --
> James P. Kinney III
> I would rather stumble along in freedom than walk effortlessly in chains.
>
>
>  Proud partner. Susan G. Komen for the Cure.
>
>  *Please consider our environment before printing this e-mail or
> attachments.*
>  ----------------------------------
> CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential
> information and is for the sole use of the intended recipient(s). If you are
> not the intended recipient, any disclosure, copying, distribution, or use of
> the contents of this information is prohibited and may be unlawful. If you
> have received this electronic transmission in error, please reply
> immediately to the sender that you have received the message in error, and
> delete it. Thank you.
> ----------------------------------
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>


-- 
-- 
James P. Kinney III
I would rather stumble along in freedom than walk effortlessly in chains.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20101008/b07db6a6/attachment-0001.html