Profiling a Truffle language
gerard at gerardkrol.nl
Sun Jul 31 19:05:04 UTC 2016
Thanks, that was very helpful. It was quite hard to get it working, but I
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 copy
the class over (just adding a derived class with the annotation worked as
Chris, the slow part does seem to be the array copy part, not sure why as
Cover is fully typed so all nodes have just a single specialization. I'm
On Sun, Jul 31, 2016 at 12:13 PM, Stefan Marr <java at stefan-marr.de> wrote:
> 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 program.
> > something like that available or will I have to write something myself?
> > 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