From: Julien Desfossez <jdesfossez@efficios.com>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>,
diamon-discuss@lists.linuxfoundation.org
Cc: Antoine Busque <antoine.busque@efficios.com>
Subject: [diamon-discuss] [RELEASE] LTTng-analyses v0.2
Date: Mon, 25 May 2015 15:51:12 -0400 [thread overview]
Message-ID: <55637D30.7050604@efficios.com> (raw)
Hi everyone,
I am glad to announce the second release of the lttng-analyses project !
https://github.com/lttng/lttng-analyses
This project is a collection of tools to extract metrics and
higher-level informations from LTTng kernel traces.
This is mostly a one-man-release: Antoine Busque did all the work of
refactoring, cleaning up the code and fixing a number of bugs.
Thanks to this work, we know have a nice architecture that will allow us
to add more analyses and integrate with other tools.
The implemented analyses did not change from the previous release, but
you might notice some differences from the output of the previous release:
- CPU usage per-process and system-wide
- Process CPU migration count
- Memory usage per-process and system-wide (as seen by the kernel)
- I/O usage (syscalls, disk, network)
- I/O operations log (with latency and usage)
- I/O latency statistics (aggregated open, read, write, sync operations)
- I/O latency frequency distribution
- Interrupt handler duration statistics (count, min, max, average stdev)
- Interrupt handler duration top
- Interrupt handler duration log
- Interrupt handler duration frequency distribution
- SoftIRQ handler latency statistics
- Syscalls usage statistics
We appreciate all kinds of feedback, use-cases and real-world
experiences, so please test it and let us know what you think about it.
Julien
reply other threads:[~2015-05-25 19:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55637D30.7050604@efficios.com \
--to=jdesfossez@efficios.com \
--cc=antoine.busque@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=lttng-dev@lists.lttng.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.