This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [pcp] suitability of PCP for event tracing
- From: David Smith <dsmith at redhat dot com>
- To: Ken McDonell <kenj at internode dot on dot net>
- Cc: "Frank Ch. Eigler" <fche at redhat dot com>, systemtap at sources dot redhat dot com
- Date: Wed, 01 Sep 2010 10:05:06 -0500
- Subject: Re: [pcp] suitability of PCP for event tracing
- References: <20100827153906.GD3185@redhat.com> <4C7A82D1.50602@internode.on.net>
On 08/29/2010 10:54 AM, Ken McDonell wrote:
... stuff deleted ...
> As Nathan has suggested, if event traces are intended for retrospective
> analysis (as opposed to event counters being suited for either real time
> or retrospective analysis), then there is an alternative approach,
> namely to create a PCP archive directly from a source of data without
> involving pmcd or a pmda or pmlogger. We've recently reworked the
> "pmimport" services to expose better APIs to support just this style of
> use ... see LOGIMPORT(3) and sar2pcp(1) for an example. I think this
> approach is possibly a better semantic match between PCP and a stream of
> event records.
Hmm. If I'm understanding all the acronyms correctly, I'm not seeing
the benefit of using LOGIMPORT to create a PCP archive vs. involving
pcmd/pmda/pmlogger. Could you expand here?
Thanks.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)