[mercury-users] Memory profiling

[Paul Bone]

On Tue, Jan 04, 2011 at 12:45:50PM +1100, Julien Fischer wrote:
> 
> On Sun, 26 Dec 2010, Michael Day wrote:
> 
> >As a result, it's impossible to tell from the profile which
> >allocated memory is persisting for the life of the program, and
> >thus affecting the maximum memory usage, and which allocated
> >memory is quickly collected, leading to garbage collection churn
> >but no extra memory requirements.
> >
> >Is there any way of figuring out at a particular point in time
> >during program execution where the currently used memory was
> >allocated?
> 
> Not that I know of.

Nothing like this is currently implemented, but it should be possible to
implement it in a profiling grade using the GC's finalizers.  However this will
probably make profiling _a lot_ slower and be time-consuming to implement.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.mercurylang.org/archives/users/attachments/20110104/f494704a/attachment.sig>