[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Finding Octave's memory use breakdown
From: |
morgawr |
Subject: |
Re: Finding Octave's memory use breakdown |
Date: |
Fri, 1 Jul 2016 15:37:24 -0700 (PDT) |
Perhaps you want valgrind massif. It shows memory usage at "snapshots" in
time (measured in instructions executed). It is quite fast. Eg:
valgrind --tool=massif --stacks=yes --massif-out-file=some_name
octave-cli-4.1.0+ --eval 'quit'
ms_print some_name
user options for Massif:
--heap=no|yes profile heap blocks [yes]
--heap-admin=<size> average admin bytes per heap block;
ignored if --heap=no [8]
--stacks=no|yes profile stack(s) [no]
--pages-as-heap=no|yes profile memory at the page level [no]
--depth=<number> depth of contexts [30]
--alloc-fn=<name> specify <name> as an alloc function [empty]
--ignore-fn=<name> ignore heap allocations within <name> [empty]
--threshold=<m.n> significance threshold, as a percentage [1.0]
--peak-inaccuracy=<m.n> maximum peak inaccuracy, as a percentage [1.0]
--time-unit=i|ms|B time unit: instructions executed, milliseconds
or heap bytes alloc'd/dealloc'd [i]
--detailed-freq=<N> every Nth snapshot should be detailed [10]
--max-snapshots=<N> maximum number of snapshots recorded [100]
--massif-out-file=<file> output file name [massif.out.%p]
--
View this message in context:
http://octave.1599824.n4.nabble.com/Finding-Octave-s-memory-use-breakdown-tp4676477p4678120.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: Finding Octave's memory use breakdown,
morgawr <=