Hmm. I think my answer here is the wrong kind of answer. Someone
asks for a profiling system (i.e., a way to collect *real* data), and
I respond with a random guess about why the application in question is
slow.
Guile has no profiling support that I know of. It's a very good idea,
and badly needed. Some people have profiled the Guile interpreter
itself, at the C level. That's helpful if C primitives are consuming
most of your time, but if it says you're spending 90% of your time in
eval, then that's not very helpful.
I'd encourage folks to take a stab at this; post your code to the
list.