Hello,

I've been having a grand old time with the 'time' macro, investigating the effects of subtle code changes. But for large programs, a profiler would be much better.

Aziz, is there a profiler available for Ikarus? I'm more interested in finding out where my program is spending the majority of it's time, as opposed to "number of times a procedure is called". Even if you have an experimental one laying around, I'd be happy to try it.

I've considered running my code in another Scheme for the profiler. For example, DrScheme has a profiler. Also, Larceny comes with an experimental profiler (lib/Debugger/profile.sch). One concern I have is that the results would be of limited use if the different systems use different compilation/optimization techniques. I.e. I really should run the profiler on Ikarus if that's the system I want my code to run fast on.

One minor hurdle in the way of using the DrScheme profiler is that it requires an '#!r6rs' at the top of every file... Sure, I could add that but it seems silly when every other implementation I use doesn't demand it.

Ed

Reply via email to