On Fri, May 02, 2003 at 02:56:45AM +0200, Peter Simons wrote:

Kirsten Chevalier writes:

...

I'm running GHC with the following options: -fallow-overlapping-instances -cpp -O1 -fvia-C -fglasgow-exts -package text -dcore-lint -prof -auto-all +RTS -K48M -M1024M -RTS -fno-strictness -Rghc-timing

Did you try setting a bigger "suggested heap size" for GHC with the run-time-system option "-H"? I found that setting something like "-H128M" affected compile times positively on my machine.

I hope this helps ...

I tried compiling the same file with -H512M -M512M instead of -M1024M, keeping all other options the same. I got the following results: <<ghc: 3763646968 bytes, 33 GCs, 17879484/44290920 avg/max bytes residency (6 samples), 528M in use, 0.00 INIT (0.83 elapsed), 54.89 MUT (116.82 elapsed), 9.58 GC (11.56 elapsed) :ghc>> With -O0, I get: <<ghc: 1482033536 bytes, 26 GCs, 9519452/29147696 avg/max bytes residency (5 samples), 515M in use, 0.00 INIT (0.28 elapsed), 15.27 MUT (69.29 elapsed), 2.63 GC (2.92 elapsed) :ghc>> This is better than before, but it still seems pretty slow; any other suggestions? Thanks, Kirsten -- Kirsten Chevalier * krc@uclink.berkeley.edu * Often in error, never in doubt