From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug testsuite/10671] New: semok/twenty.stp takes 15 minutes on
Date: Sun, 20 Sep 2009 16:52:00 -0000 [thread overview]
Message-ID: <20090920165213.10671.mjw@redhat.com> (raw)
The semok/twenty.stp test takes 15 minutes on my slow laptop. The test simply
consists of all dwarfable probes for the kernel and all modules:
probe kernel.function("*") {}
probe module("*").function("*") {}
probe kernel.function("*").call {}
probe module("*").function("*").call {}
probe kernel.function("*").return {}
probe module("*").function("*").return {}
probe kernel.function("*").inline {}
probe module("*").function("*").inline {}
It looks like on this system processing of almost 2000 modules takes most of
that time (the machine has a slow disk and "only" 1.5GB of memory).
--
Summary: semok/twenty.stp takes 15 minutes on
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mjw at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10671
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-09-20 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 16:52 mjw at redhat dot com [this message]
2009-09-20 16:52 ` [Bug testsuite/10671] semok/twenty.stp takes 15 minutes on slow/low-memorry machine mjw at redhat dot com
2009-09-20 18:45 ` mjw at redhat dot com
2009-09-20 23:33 ` fche at redhat dot com
2009-09-21 0:01 ` fche at redhat dot com
2009-09-22 9:39 ` mjw at redhat dot com
2009-09-22 9:57 ` mjw at redhat dot com
2009-09-22 10:10 ` [Bug testsuite/10671] semok/twenty.stp takes 15 minutes on slow/low-memory machine mjw at redhat dot com
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=20090920165213.10671.mjw@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).