Profiling a Truffle language
christian.humer at gmail.com
Sun Jul 31 19:15:01 UTC 2016
On 31.07.2016 21:05:04, "Gerard Krol" <gerard at gerardkrol.nl> wrote:
>Thanks, that was very helpful. It was quite hard to get it working, but
>managed. For me it's still called TruffleProfiler (version 0.15 of
>Truffle). Weirdly enough it was not picking up the class from the
>truffle-debug jar through the @Registration annotation, so I had to
>the class over (just adding a derived class with the annotation worked
Sorry to hear that. Did you put the truffle-debug.jar on the normal or
boot classpath? Could you maybe copy in your java command line that you
were using, so I can potentially reproduce it?
Please also note that this version of the TruffleProfiler is based on
instrumentation and is quite heavy. Therefore its results might not be
A more lightweight version based on sampling is coming soonish (1-3
weeks) to the Truffle tip.
>Chris, the slow part does seem to be the array copy part, not sure why
>Cover is fully typed so all nodes have just a single specialization.
>On Sun, Jul 31, 2016 at 12:13 PM, Stefan Marr <java at stefan-marr.de>
>> Hi Gerard:
>> > On 31 Jul 2016, at 11:45, Gerard Krol <gerard at gerardkrol.nl> wrote:
>> > What I'd like to have is a simple profiler (preferably one using
>> > that will point me to the actual slow statements in the source
>> > something like that available or will I have to write something
>> > the last case, I suppose I should be using the the Truffle
>> > API?
>> There is a profiler already in the instrumentation framework.
>> I am not entirely sure, but I think the class is now named Profiler.
>> Things seem to have changed.
>> I am using it in SOMns:
>> And I wrote some related notes up here:
>> For the profiler, you’ll need to tag some node in each method as Root
>> Or perhaps easier to find in the SimpleLanguage:
>> Hope that gets you started.
>> Best regards
>> Stefan Marr
>> Johannes Kepler Universität Linz
More information about the graal-dev