Has anyone ever profiled Csound in order to see where time is spent in the 
program, and to optimize the code? And if so, when?

If not, I'm going to try some profiling; I've just had some good results on 
another project.

Regards,
Mike 


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

As far as I can remember Istvan and myself did a little profiling; it
was this that led to the code change from pointer arithmetic to array
access in the loops on ksmps.  Not much since of which I am aware.  I
have rarely used valgrind on it to look for memory problems.
==John ffitch

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net