From: "zhenyu.ren" <zhenyu.ren@aliyun.com>
To: lttng-dev <lttng-dev@lists.lttng.org>
Subject: How to analysis a huge trace-collected data efficiently
Date: Thu, 11 Sep 2014 09:38:07 +0800 [thread overview]
Message-ID: <e4797186-ccb1-4efc-a68e-953e8575a42a__18243.1339323104$1410399545$gmane$org@aliyun.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 495 bytes --]
Hi, It's well known that tracing can produce huge data easily.So if we keep tracing on a production system for a while(hour/day/week) ,we may get a huge CTF file. It's very inefficient to analysis a huge CTF file ,especially the interested events are in some narrow time window.Is there any way to change the situation?Can we split a huge ctf file into several small ctf file? Or can lttng produce a list of small time-sequence ctf filles just like some loggers do?Thankszhenyu.ren
[-- Attachment #1.2: Type: text/html, Size: 1080 bytes --]
[-- Attachment #2: Type: text/plain, Size: 155 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2014-09-11 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 1:38 zhenyu.ren [this message]
[not found] <e4797186-ccb1-4efc-a68e-953e8575a42a@aliyun.com>
2014-09-11 11:32 ` How to analysis a huge trace-collected data efficiently Michel Dagenais
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='e4797186-ccb1-4efc-a68e-953e8575a42a__18243.1339323104$1410399545$gmane$org@aliyun.com' \
--to=zhenyu.ren@aliyun.com \
--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.