From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966840AbbBDQMY (ORCPT ); Wed, 4 Feb 2015 11:12:24 -0500 Received: from fukushima.klipix.org ([85.12.144.25]:43185 "EHLO fukushima.klipix.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966581AbbBDQMV (ORCPT ); Wed, 4 Feb 2015 11:12:21 -0500 X-Greylist: delayed 354 seconds by postgrey-1.27 at vger.kernel.org; Wed, 04 Feb 2015 11:12:20 EST Message-ID: <54D2437D.7030802@efficios.com> Date: Wed, 04 Feb 2015 11:06:21 -0500 From: Julien Desfossez User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "lttng-dev@lists.lttng.org" CC: diamon-discuss@lists.linuxfoundation.org, linux-kernel@vger.kernel.org Subject: [RELEASE] LTTng-analyses v0.1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi everyone, I am glad to announce the very first 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. Here is a complete example that illustrates how to solve a real-world problem with this project: http://lttng.org/blog/2015/02/04/web-request-latency-root-cause/ The workflow with these tools is different from the traditional debugging/monitoring tools. We trace the whole system and then analyse the trace offline. So the cost of analysing the trace is done outside of production. The project benefits from the low overhead of LTTng to mostly target hard to identify performance/latency problems. Here is the list of the implemented analyses in this 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. I would like to thank everyone who contributed ideas, code, reviews and funding on this project that started almost a year ago ! Julien