[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Finding Octave's memory use breakdown
From: |
Juan Pablo Carbajal |
Subject: |
Re: Finding Octave's memory use breakdown |
Date: |
Mon, 25 Apr 2016 09:04:18 +0200 |
On Mon, Apr 25, 2016 at 5:42 AM, LachlanA <address@hidden> wrote:
> Greetings all,
>
> Is there a way to find out where Octave is using memory? I often find that
> Octave is using say 2GB, but "whos" shows only a few hundred megabytes in
> variables. I assume that much of it is in the libraries, some is in
> Octave's own code, some of it is in overhead for variables (like field names
> in an array of structs), some of it is in parse trees, etc..
>
> The thing that triggered this post was Kai's suggestion to replace printf by
> a .m file. The main advantage I can see is to reduce the size of the
> executable, which got me wondering where the memory all goes.
>
> Similarly, I've heard that allocating memory was one of the big consumers of
> time. Does anyone have a breakdown of what fraction of allocations come
> from each class of memory use?
>
> I used to think that Valgrind would be able to tell me that sort of thing,
> but I've never found the right invocation.
>
> Thanks,
> Lachlan
>
>
>
> --
> View this message in context:
> http://octave.1599824.n4.nabble.com/Finding-Octave-s-memory-use-breakdown-tp4676477.html
> Sent from the Octave - Maintainers mailing list archive at Nabble.com.
>
See if memory from here helps you
https://github.com/kakila/macgyver_utils/blob/master/memory.m