From: "Maciej Borzęcki" <maciej.borzecki@rndity.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: is there a list somewhere of OE/YP-supported system perf/monitoring tools?
Date: Wed, 8 Feb 2017 13:12:08 +0100 [thread overview]
Message-ID: <CAD4b0_JRJa+xyg5QrJarbRD-PCZ3=aAtK56iBBx7mUX9_eysrQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1702080702070.12201@localhost.localdomain>
On Wed, Feb 8, 2017 at 1:02 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Wed, 8 Feb 2017, Maciej Borzęcki wrote:
>
>> On Tue, Feb 7, 2017 at 3:31 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>> >
>> > colleague asked me for a list of OE/YP recipes for monitoring system
>> > performance/resource utilization/profiling, i'm unaware of any single
>> > list that tracks that sort of thing so i'll just ask what people are
>> > aware of. just off the top of my head:
>> >
>> > * sysstat
>> > * atop
>> > * collectd
>> > * netdata
>> > * rrdtool
>> > * dstat
>>
>> * pcp http://pcp.io/
>
> is there an OE recipe for that? i don't see one.
Sadly not :( The build system is based on autotools though. Most of
the 'heavy' features can be easily turned off using configure.
--
Maciej Borzecki
RnDity
prev parent reply other threads:[~2017-02-08 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 14:31 is there a list somewhere of OE/YP-supported system perf/monitoring tools? Robert P. J. Day
2017-02-08 6:48 ` Maciej Borzęcki
2017-02-08 11:38 ` Gary Thomas
2017-02-08 11:45 ` Leon Woestenberg
2017-02-08 11:51 ` Robert P. J. Day
2017-02-08 12:06 ` Robert P. J. Day
2017-02-08 13:59 ` Joshua Lock
2017-02-08 14:11 ` Robert P. J. Day
2017-02-08 12:02 ` Robert P. J. Day
2017-02-08 12:12 ` Maciej Borzęcki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD4b0_JRJa+xyg5QrJarbRD-PCZ3=aAtK56iBBx7mUX9_eysrQ@mail.gmail.com' \
--to=maciej.borzecki@rndity.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.