[Openmcl-devel] Profiling

[Gail Zacharias]

At 3/1/2010 03:36 PM, Ian Eslick wrote:
>Very helpful!  That goes a long way to helping me solve my 
>problem.  I saw a reference to it in an old message, but I had no 
>idea it was in the tools directory.  (Be nice to add at least a 
>simple pointer into the online docs about profiling)
>
>The consing reports are very helpful.  Is there a way to extend that 
>code to identify memory allocation by arrays, hash-tables, and strings too?

I know it's not exactly the same sort of thing, but perhaps 
ccl:heap-utilization 
(http://trac.clozure.com/ccl/wiki/HeapUtilization) would be helpful.


>Thank you,
>Ian
>
>On Mar 1, 2010, at 11:06 AM, Hans Hübner wrote:
>
> > Ian,
> >
> > On Mon, Mar 1, 2010 at 19:57, Ian Eslick <eslick at media.mit.edu> wrote:
> >> Scraping the clozure site and mailing lists I've come to the 
> following conclusion:
> >>
> >> 1) CHUD support doesn't work with 4.6 and while it used to work 
> with 4.5 doesn't anymore
> >> 2) oprofile is the only method of profiling other than (time ...)
> >
> > I may be lacking important context, but the advice profiler
> > (tools/advice-profiler/) might be worth considering.
> >
> > -Hans
>
>_______________________________________________
>Openmcl-devel mailing list
>Openmcl-devel at clozure.com
>http://clozure.com/mailman/listinfo/openmcl-devel