From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/10234] New: clean up aggregate hard-coded logic
Date: Wed, 03 Jun 2009 17:45:00 -0000 [thread overview]
Message-ID: <20090603174445.10234.fche@redhat.com> (raw)
the runtime makes a number of unfortunate assumptions about aggregate objects:
- that all of count/min/max/sum should be tracked
- that only one or other type of histogram can be attached to it
So this should work:
global x
probe begin {x <<< 1}
probe end {println(@count(x))}
... and without tracking sums/maxima/whatever. This is an optimization.
and this:
global x
probe begin { x <<< 1 }
probe end {println(@hist_linear(x, 0, 10,1)
println(@hist_linear(x, 20,40,1))
This is a missing feature. (Perhaps we could hack around this limitation
in the translator by forking the "x" variable internally, but it would not
help the memory consumption if e.g. x was an array of aggregates.)
--
Summary: clean up aggregate hard-coded logic
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10234
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-06-03 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 17:45 fche at redhat dot com [this message]
2009-06-03 17:49 ` [Bug runtime/10234] " fche at redhat dot com
2009-06-03 18:01 ` leitao at linux dot vnet dot ibm dot com
2009-06-03 18:18 ` jkenisto at us dot ibm 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=20090603174445.10234.fche@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).