Changes between Version 6 and Version 7 of GhcPlanning


Ignore:
Timestamp:
Nov 17, 2006 2:16:02 PM (8 years ago)
Author:
simonmar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GhcPlanning

    v6 v7  
    4848   to know about this change. 
    4949 
     50 * '''Ghc Performance Index''' (#1009). 
     51 
     52 * '''libffi''' 
     53 
    5054Simon PJ's projects 
    5155 * '''Lambda match''' Look at Claus' patch 
     
    6468This list intended to be in priority order (but of course the prorities might not be right! 
    6569 
    66  * '''Long-term benchmarking'''  Simon & I were talking over coffee this morning about having a lightweight way to detect when either (a) the compiler's performance changes, or (b) the performance of compiled code changes.  This was triggerred by my noticing that the HEAD nightly builds seem somewhat slower than usual right now. 
    67  
    68   So the idea is pretty simple.  We decide on a fixed set of nofib programs --intiially all of them, but we want the set to remain stable in the future -- and as part of the nightly build we time how long it takes to compile this set with a fixed set of flags (probably -O -fasm, to rule out changes in gcc).  Then we time how long it takes to run all those programs, maybe 5 times each.  Then we keep track of these two figures for every successful nightly build, and plot the results, giving us a nice way to track GHC's performance over time.  We can go back and get some historical figures too.  Of course the results are specific to a particular machine, so we'd have to keep track of results per nightly build machine or something. 
    69  
    70   So basically: some small changes to nofib to allow "just build everything" (I think even NoFibRuns=0 might do this), and to build a fixed set of programs (the set could be built into the nofib build system, no need to make it dynamic).  And some way to collect the results and plot graphs.  What do you think? 
    71  
    72  * '''libffi''' 
    73  
    74  * '''Integrating coverage testing.'''  What's involved here? 
    75  
    7670 * '''Windows installers'''. Want to help Neil get going 
    7771