Instrumented Profiler
Allocating objects is expensive. The shorter an object's lifetime is, the less expensive it is in total. But what happens to objects that only live for a few instructions? This post shows off how "scalar replacement" looks in the profiler frontend.
Instrumented Profiler
Getting an overview of a program's performance also means you've got to have an idea which routines are responsible for what. A "flame graph" does this very well.
grant
A week and a half after the previous work report on the MoarVM profiler frontend, here is another. This time it features changes to the overview page and a search feature for the call graph.
grant
My report of improvements and additions to the perl6 profiler frontend UI since the last post.
grant
I got a whole lot of work done since the previous post. The "Routines" tab is now quite useful, and there's a "Call Graph Explorer" as well! Check the full post for download/usage instructions
grant
I've been working on the profiler's GC display for the past weeks. Here's my report, including a comparison against the old one.
grant
Sadly, the time since the last post on this blog hasn't been fruitful with regards to the profiling project.
grant
Just these past few days I've made a bit of reliability work for the profiler available to everyone running rakudo from the latest source code.