search

namme-anetten / epigram

Automatically exported from code.google.com/p/epigram
0 stars 0 forks source link

Profiling infrastructure #41

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
It looks like some time is being spent on optimizing "stuffs". I'm extremely 
worried by un-targeted optimization efforts. Premature optimization is a vain 
expression, until you discover that you've ruined your source code.

To prevent this, there is exist a simple cure: to know where time is spent. For 
this, you can try black magic, or you can use Haskell support for profiling. I 
can but recommend the second option.

To have an infrastructure set up, we need a fully-automated script that runs 
the test suite and directly outputs graphs for memory and time usage. 

We also want to declare SCCs in the source code (and have lhs2TeX not to choke 
on them).

References: 

http://hackage.haskell.org/package/prof2dot
http://www.haskell.org/ghc/docs/6.12.2/html/users_guide/profiling.html
http://book.realworldhaskell.org/read/profiling-and-optimization.html

Original issue reported on code.google.com by pedag...@gmail.com on 11 Aug 2010 at 6:53

GoogleCodeExporter commented 9 years ago

Original comment by pedag...@gmail.com on 11 Aug 2010 at 6:55