Very cool but also more interesting is using Perl for any newish project.
It is hard to find maintainers or developers knowing Perl nowadays. Especially in data science related projects as python has been the de-facto tool for that field for some time now.
Hah I did this for SQL Server execution graphs at one point (via profiler or extended events) and then I of course realized that anything that goes more than one or two events deep is just hellish SQL anyway, love to see the execution plan version that's much smarter.
If I were in vgrippa's place, I would have not produced flamegraphs, but treemaps. It's the far superior choice for visualising profiling/query plans and the like, no matter along which property one would measure.
Munging the mysql output into something that is delectable as input to kcachegrind is straight-forward. Screenshots: https://ddg.gg/?q=%21i+kcachegrind
ab_testing|18 days ago
It is hard to find maintainers or developers knowing Perl nowadays. Especially in data science related projects as python has been the de-facto tool for that field for some time now.
vgrippa|18 days ago
hobs|19 days ago
bonesss|19 days ago
Data science <pew pew>!
bmn__|18 days ago
Munging the mysql output into something that is delectable as input to kcachegrind is straight-forward. Screenshots: https://ddg.gg/?q=%21i+kcachegrind
vgrippa|18 days ago
I will take a look at the treemaps and try to incorporate.
dveeden2|19 days ago
This was part of the MySQL Belgian Days that was organized in the days before FOSDEM.
lofaszvanitt|19 days ago
lofaszvanitt|19 days ago
vgrippa|18 days ago
The slides can be found here: https://github.com/vgrippa/presentations/blob/main/2026_FOSD...
javier2|19 days ago
vgrippa|23 days ago