github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
MasterDuke timotimo: hm, could we start profiling, enter/exit a frame a bunch, figure out how long that took, end profiling, discard what we've collected, and then start profiling again? 00:29
brrt \o 07:02
nwc10 o/ 07:04
lizmat MasterDuke: am working on a Perl 6 interface to the profiling info 07:04
see lib/MoarVM/Profiler.pm6 for WIP 07:05
timotimo the MoarVM::Profiler module could perhaps be something to get some unit tests that would at least find the worst breakages 07:28
Geth MoarVM/configurable-subsystems: 6 commits pushed by (Timo Paulssen)++ 08:37
timotimo oh
oh no
gitg's "discard selection" doesn't mean "unselect everything", it means "remove the selected changes from the files" 08:39
well, that's fun
that explains why it opens up a confirmation dialog 08:43
that i immediately clicked "ok whatever" on
Geth MoarVM/configurable-subsystems: 7252cb0aa9 | (Timo Paulssen)++ | 3 files
restore some changes that almost got nuked
timotimo fortunately "changes outside of vim detected, reload buffer from disk?" can be undone simply with the undo command 08:45
MasterDuke lizmat: i've seen the commits go by, glad to see all the enhancements to profiling. however, what i was asking about would have to take place in moarvm, an initial step to `profile` the cost of profiling a function so we can exclude that from the reported cost 11:07
lizmat MasterDuke: oki :-)
MasterDuke lizmat: it's the sort of thing that might make sense to expose as an option to exclude or not via the api you have, since it won't be exact and someone might want the values included 12:08
lizmat afaik, the values returned by nqp::mvmendprofile are from code run since nqp::mvmstartprofile 12:13
and they're by thread
brrt good *
lizmat so I don't think there's actually any additional hidden cost ?
brrt lizmat: for the weekly, can you say that GSoC has started, that we have 2 new students working on MoarVM (and I think, one on perl6 documentation), and that (at least) one student already has a PR merged? :-) 12:16
lizmat do we have a link to the projects ?
brrt let me get it... 12:22
summerofcode.withgoogle.com/dashbo.../overview/ - dunno if this is a public link though 12:24
lizmat nope, needs a login :-(
brrt summerofcode.withgoogle.com/organi...599357952/ this ought to be a public link though
lizmat yup, it is, thanks! 12:29
MasterDuke lizmat: i think the cost of the profiling functionsMVM_profile_log_(enter|exit) are being included. iirc, that's why jnthn said `identity` has more that zero exclusive time in many of my profiles (it's essentially a no-op normally, but the added profiling functions means it can't be entirely removed) 12:36
lizmat ah, like that... hmmm
yeah, removing "indentity" from the profile usually makes sense :-) 12:37
MasterDuke so subtracting out the estimated cost of profiling should drop `identity` to near the bottom of profiles 12:39
lizmat and another Perl 6 Weekly hits the Net: p6weekly.wordpress.com/2019/05/27/...thats-why/ 14:07
brrt \o 20:11
jnthn o/ 20:31
timotimo \o 21:37
brrt and just like that, it was too late already... 21:39
timotimo were you planning something?
brrt fixing the world 21:46
timotimo oh, you know, being boiled to death isn't such a bad way to go 21:47
timotimo oh, the instrumented profiler leaks 100% of its collected data btw, haha 23:15
because so far the next thing after a profiler run has ended was that the program would output the data to a file and quit
but freeing all the data before returning the hash/list datastructures would be good for memory usage, too. as in, the dumping code could be run with much less memory pressure 23:17
MasterDuke timotimo: that would be good, I’ve had profiles get killed by the oom killer when writing them out 23:56

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!