Re: [racket-users] Profiling help

2016-01-16 Thread Vincent St-Amour
Looks like that run had more useful info. Your uses of `string-trim` and `fprintf` are probably worth investigating. Vincent On Sat, 16 Jan 2016 21:01:22 -0600, Brian Adkins wrote: > > On Saturday, January 16, 2016 at 9:40:51 PM UTC-5, Vincent St-Amour wrote: > > Brian, > > > > The Racket pr

Re: [racket-users] Profiling help

2016-01-16 Thread Brian Adkins
On Saturday, January 16, 2016 at 9:40:51 PM UTC-5, Vincent St-Amour wrote: > Brian, > > The Racket profiler is an edge profiler. So in addition to telling you > which code time is spent in, it's also telling you which callers caused > which proportion of that time. > > In the case of [48], it's t

Re: [racket-users] Profiling help

2016-01-16 Thread Vincent St-Amour
Brian, The Racket profiler is an edge profiler. So in addition to telling you which code time is spent in, it's also telling you which callers caused which proportion of that time. In the case of [48], it's telling you that file output is a significant bottleneck, and that it's caused by the code

[racket-users] Profiling help

2016-01-16 Thread Brian Adkins
I'm not sure if something changed with 6.3, but I have the output of: racket -l errortrace -t parser.rkt in the following gist: https://gist.githubusercontent.com/lojic/9cd8a3a88ef2e110b9de/raw/79e9892326101333d11987c8e3a3b9df93adc63a/profile%2520output I'm having trouble understanding the outp