public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Lukas Berk <lberk@redhat.com>
To: Jon VanAlten <jvanalte@redhat.com>
Cc: systemtap@sourceware.org, distro-pkg-dev@openjdk.java.net
Subject: Re: [RFC] Enhanced Garbage Collection Probe Points
Date: Wed, 08 Aug 2012 21:11:00 -0000	[thread overview]
Message-ID: <20120808211122.GA17399@redhat.com> (raw)
In-Reply-To: <1956303607.34675944.1344458257034.JavaMail.root@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2459 bytes --]

* Jon VanAlten <jvanalte@redhat.com> [2012-08-08 16:38]:
[...]
> 
> Hi Lukas,
> 
> I've had a look at the patch, and the rest of the thread (especially the
> tapset you posted, which made things a LOT more clear so thanks for that).
> I hope that you'll continue to refine the tapset and contribute that as
> well so that us java hackers who are brave enough to play with Systemtap
> have the nice friendly probe names and variables to work with!
Thanks for taking a look, I'll make sure to include it in future
revisions, ideally I'll have a gc_details.stp.in file that will have the
.so path change based on the system it's being compiled for. (similar to
the hotspot{,_jni}.stp.in and jstack.stp.in files already included)
> 
> The patch itself seems fine, although I'll just have to trust you that the
> probes are in the right place as I'm not really a hotspot hacker myself.
> Really I would hope that someone who is more familiar with the GC code
> base will comment from that perspective.
> 
> I assume that none of these probes require any special VM args to function?
> A related question, and this might be hard to answer being rather open
> ended, but are you aware of any VM args that would affect/interfere with
> the functioning of these probes?
The only arguments that I can think of that will immediately effect
these probes are:
-XX:+UseSerialGC
-XX:+UseParallelGC
-XX:+UseParallelOldGC
-XX:+UseParNewGC
-XX:+UseConcMarkSweepGc
-XX:+UseG1GC
which will force the JVM to use the designated type of garbage
collection.  There may be more I'm missing (please let me know if there
are).
> 
> There is a begin and and end probe for some types of collection and even
> phases within collection, so it seems odd to me that for G1 stop-the-world
> collection there is not.  Am I missing something?

My thought in adding the begin/end probes was to be able to track
parallel operations and tie a specific pid to an collection/scavenge to
an object.  That wouldn't be needed in serial operation.  However, now
that I think about it, it could be useful to mark the beginning and end
of 'serial' collections from a timing perspective, and its trivial to
add (I'll include it in a revised patch).
> 
> Other than that; great start, this definitely has stuff interesting from a
> Thermostat perspective and the potential for more :D
> 

Thanks for the comments,

Lukas

[1] - http://dacapobench.org/

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-08-08 21:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 13:11 Lukas Berk
2012-08-03 13:56 ` Mark Wielaard
2012-08-03 14:23   ` Lukas Berk
2012-08-07 11:50     ` Mark Wielaard
2012-08-08 14:01       ` Lukas Berk
2012-08-08 14:34         ` Mario Torre
2012-08-08 20:37 ` Jon VanAlten
2012-08-08 21:11   ` Lukas Berk [this message]
2012-08-08 22:05     ` Jon VanAlten
2012-08-22 20:34 ` Lukas Berk
2012-08-24 19:59   ` Jon VanAlten
2012-08-28 21:23     ` Lukas Berk
2012-08-29 11:52       ` Mark Wielaard
2012-08-30  1:19       ` Jon VanAlten
2012-08-31 20:07         ` Lukas Berk
2012-09-24 18:17           ` Jon VanAlten
2012-10-23 16:53             ` Lukas Berk
2012-10-25  5:02               ` Jon VanAlten
2012-10-25 13:09                 ` Andrew Hughes
2012-10-30  1:49                   ` Jon VanAlten
2012-10-30  8:03                     ` Mark Wielaard
2012-10-30 12:37                     ` Andrew Hughes
2012-11-01 18:33                       ` Jon VanAlten
2012-11-01 19:06                         ` Mark Wielaard
2012-11-01 22:12                           ` Jon VanAlten
2012-11-02 14:54                           ` Andrew Hughes
2012-11-02 15:03                             ` Mark Wielaard

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=20120808211122.GA17399@redhat.com \
    --to=lberk@redhat.com \
    --cc=distro-pkg-dev@openjdk.java.net \
    --cc=jvanalte@redhat.com \
    --cc=systemtap@sourceware.org \
    /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).