Yesterday, Danny Yoo wrote:
> >
> > http://stackoverflow.com/questions/54971/profiling-visualization-tools
> >
> > which has a number of pointers that look useful. It also looks
> > like graphviz is the most popular recommendation, so perhaps
> > that's the best way to go -- slapping a GUI or an HTML rendering
> > around it.
>
> As an example of the kind of documentation I'd like to see, one of the
> Go folks wrote up how to use their profiler tools:
>
> http://blog.golang.org/2011/06/profiling-go-programs.html
>
> and I would love it if we had some similar documentation.
JFYI, I have revised the documentation, which had a bunch of pretty
bad points. But that's probably not what you want; hopefully my
earlier reply was helpful, and more hopefully someone will write up a
"guide" part for the docs, to similarly clarify things.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_________________________________________________
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/users
