[plt-scheme] Profiling code

From: Noel Welsh (noelwelsh at gmail.com)
Date: Wed Oct 22 10:57:08 EDT 2008

If you lower the log level (search for "Logging" in the docs) GC stats
and other information will become available.  This might help you.


On Tue, Oct 21, 2008 at 6:19 PM, Deep <deepankar.sharma at gmail.com> wrote:
> My game prototype in DrScheme is now feature complete and I would like
> to optimise it to make things run faster. The inbuilt profiler is
> wonderfully well integrated and has already helped me remove some
> bottlenecks.
> However there are a few functions in my code that get called very
> often and have a very small execution time. I want to know if there is
> an additional cost in terms of "function call overhead" that exists
> for functions beyond their actual execution time.
> On a more general note, I wanted to know how I can observe what my
> code is doing at a slightly lower level of detail. Things I would be
> interested in
> 1) How much memory is being consed.
> 2) When does GC get invoked.
> 3) What kind of assembly code is getting generated for my functions.
> 4) Am I hitting some inefficient execution paths with DrScheme.
> Any pointers if this is possible at all ?
> _________________________________________________
>  For list-related administrative tasks:
>  http://list.cs.brown.edu/mailman/listinfo/plt-scheme

Posted on the users mailing list.