How to analysis a huge trace-collected data efficiently

How to analysis a huge trace-collected data efficiently

[zhenyu.ren]

[-- 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

Re: How to analysis a huge trace-collected data efficiently

[Michel Dagenais]

[-- Attachment #1.1: Type: text/plain, Size: 638 bytes --]

Yes, if you look at the options available, you can split the trace in smaller files and even limit the total size accumulated. 

----- Mail original -----

> 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?

[-- Attachment #1.2: Type: text/html, Size: 1371 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