🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
patrickb I'm looking at `my $p = "abc" ~ "d" xx 8000; $page ~~ m/ a (.+) c /;` That consumes ~2gb of memory. The heap snapshot profiler lists top heap size at 47 MB. Does that mean, that the 2GB are definitely non-managed memory? 10:33
So is my best bet a traditional profiler and tracing mallocs in moar? 10:34
lizmat think so 10:37
MasterDuke the memory is all being allocated by copy_to, but i'm not yet sure which repr's 13:54
probably MVMString's 13:58
nope, believe it's VMArray's 14:02
i added a print of the number of the source array's elems. at one point it starts copying 64000, then 63996, then 63992, then 63988, ... 14:04
patrickb MasterDuke: Just posted stuff in the issue. 14:44
Guess it's time to revive the NFA debug logic.
The elems getting smaller seems plausible. the backtracking works itself up from the input texts full size. 14:46
lizmat And yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2023/01/16/2023-...ent-radux/ 15:15

Powered by Cro and the Raku® Programming Language.

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

Thank you!