* Andrew Myers
I've written a small driver test program that just parses the CSV, finds the minimum value for a couple of the Float fields, and exits. In the process monitor the memory usage is 6.9G before the program exits. I've tried profiling with +RTS -hc but it ran for >3 hours without finishing, it normally finishes within 4 minutes. Anyone have any ideas for me? Things to try?
It's possible that you have problems with laziness (memory being occupied by thunks). To quickly confirm this, try executing a non-profiled build with +RTS -hT. If it takes too long to complete, just abort it in the middle -- the profiling data will be written anyway (unless you kill it in a too violent way). -- Roman I. Cheplyaka :: http://ro-che.info/