From: andrew.mcdermott@windriver.com (Andrew McDermott)
Subject: [ltt-dev] limiting LTTng to a certain set of cores
Date: Thu, 12 Feb 2009 11:50:16 +0000 [thread overview]
Message-ID: <v4d4dnyivb.fsf@swi-aim.swindon.wrsec.fr> (raw)
In-Reply-To: <499311CC.2050208@polymtl.ca> (Pierre-Marc Fournier's message of "Wed, 11 Feb 2009 12:58:36 -0500")
Hi,
> Andrew McDermott wrote:
>> Is there an easy way to limit LTTng to trace a specified set of cores
>> only? I ask because in some 64+ core systems the data set collected
>> becomes too large for analysis and the tasks to be analyzed are always
>> bound to certain cores (using affinity).
>>
>
> Out of curiosity, how large is "too large"?
The "too large" actually refers to the volume or quantiy of (displayed)
events. There are a lot of event related to other cores that are of no
interest. There's no real issue with processing a multi-gigabyte trace
on the host but there are issues with transferring all 64+ channel trace
files across a very slow link.
What I'm trying to do is filter the set of data that a) needs to be
collected and b) transferred half-way around the world.
--
andy
prev parent reply other threads:[~2009-02-12 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 9:32 Andrew McDermott
2009-02-11 17:55 ` Mathieu Desnoyers
2009-02-12 11:53 ` Andrew McDermott
2009-02-11 17:58 ` Pierre-Marc Fournier
2009-02-12 11:50 ` Andrew McDermott [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=v4d4dnyivb.fsf@swi-aim.swindon.wrsec.fr \
--to=andrew.mcdermott@windriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox