From: Andrew Cagney <firstname.lastname@example.org>
To: "Frank Ch. Eigler" <email@example.com>
Cc: firstname.lastname@example.org, frysk <email@example.com>
Subject: Re: my notes from the tracing workshop
Date: Tue, 05 Feb 2008 19:02:00 -0000 [thread overview]
Message-ID: <47A8B28F.firstname.lastname@example.org> (raw)
Frank Ch. Eigler wrote:
>> There was a strong consensus that the "internal" format of the log
>> data needed to be a fast light weight database; two vendors were using
>> sqlite for instance (TPTP the eclipse tool didn't but I suspect will
>> shortly). [...]
> This seems rather wacky. If they're talking about gigabytes of trace
> traffic, a little wee in-memory database is a reach. If you need to
> do declarative querying, then you need a real database with indexes
> and whatnot. If you just need a big ass array, use BerkeleyDB. If
> you just want strongly typed flat data on disk, go XML. I wish I'd
> been there - perhaps my perceptions could have been falsified.
Right, SqLite is a little wee in-process database; it provides a
mechanism for powerful queries without the overhead of a server
implementation. Wind River presented performance numbers supporting the
approaches usability; in particular timing such as populating the
database from trace logs. While that cost is real, it is outweighed by
the benefit of being able to select arbitrary data-sets for visualization.
For system tap, provided the on-disk raw trace data format is well
defined, it will be possible to load it into SQL. BTW, while the
on-disk format could be XML, there was a general feeling that XML is
just too verbose and more compact formats intermediate forms were needed.
Can I recommend looking through the relevant slides.
>> [...] What's the status of SystemTAP on the ARM? [...]
> I haven't run it personally, but others have (Eugene Teo for the Nokia
> N800). One difficulty appears to be finding a big enough ARM box to
> self-host the kernel module build process, or else cross-compiling and
Cool, ARM support for libunwind is currently being integrated.
next prev parent reply other threads:[~2008-02-05 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47A34AA2.email@example.com>
2008-02-01 19:44 ` Frank Ch. Eigler
2008-02-05 19:02 ` Andrew Cagney [this message]
2008-02-01 16:37 Andrew Cagney
2008-02-01 22:15 ` Elena Zannoni
2008-02-05 20:37 ` William Cohen
2008-03-03 16:57 ` Andrew Cagney
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).