Hi, "Dr. Arne Babenhauserheide" <[email protected]> writes:
> Maxim Cournoyer <[email protected]> writes: > >> (call-with-mmap-bytevector >> "/gnu/store/x00bkpkikw60m9mknl3y1shsj482pxzc-llvm-21.1.1/lib/libLLVM.so.21.1" >> (compose elf-dynamic-info-soname elf-dynamic-info parse-elf)) >> => "libLLVM.so.21.1" >> --8<---------------cut here---------------end--------------->8--- >> >> I'd like to measure how much memory this consumes during execution, but >> running this in ,profile at the REPL only prints: "No samples recorded." > > Running it in a loop is the general approach to get samples recorded, > yes. But I usually check memory usage much easier: Do a lot of stuff, > then check the memory usage in top. > > (also I don’t see the memory usage in ,profile) > > This will miss parts of the effect of the gc, though, because memory > usage of guile itself seems not to get reduced after it was increased. > > You can get more precise memory information via (gc-stats). Thank you. I had overlooked (gc-stats). It looks like it contains similar information to using ,stat at the REPL, which is also useful. -- Thanks, Maxim
