Re: [Jscheme-user] profiling

[Michael R H. <bu...@cs...>]

On Thu, 2003-03-27 at 18:29, Ken Anderson wrote:
> We now have Jscheme programs that can run for several days processing data.
> 
> We'd like to have a way of profiling JScheme applications.
> 
> Compiling to java and using the java profiler doesn't work, because all procedures in a file are compiled into one Java procedure which is a giant case statement.  So timing is lumped together.  I guess i could write each procedure to its own file, but Yow!
> 
> Our concerns are localized enough we may be able to wrap some timing code at the right place an learn something.  But i thought i'd ask the group about what might be a good approach to profiling.  I'm currently thinking of locally redefining define to wrap timing code around a definition.  That way we can focus porfiling to the procedures we think are likely suspects.
> 
> Your thoughts on this topic are welcome!

I'd really like to (eventually) have a slick profiling interface in my
Eclipse plugin. If JScheme has a powerful enough backend (say,
programmatically exposed via a server port?) then I can present the data
similarly to Eclipse profiler plugin 

(screenshots: http://eclipsecolorer.sourceforge.net/ )

But I don't have any particular ideas on what to provide as I'm a long
way away from this sort of stuff (I want to have source level debugging
before I get into profiling).

-- 
Michael R Head <bu...@cs...>
Brandeis University CS graduate student