It's also entirely possible that GHC is using more memory than it really needs. We haven't done a space audit recently. Sometimes these things are program dependent. Would you like to cut down your program a bit, till it needs a mere 128M or so, and forward it to us? Or you could just wait... we are planning to look at space in the next month or so. Simon | -----Original Message----- | From: Peter Simons [mailto:simons@cryp.to] | Sent: 09 January 2003 20:54 | To: glasgow-haskell-users@haskell.org | Subject: Re: Two Questions: 'memory consumption' and '-pgmL' | | Simon Marlow writes: | | > I would try -c first (turn on the compacting collector). Adding | > more generations (eg. -G3) might help, and setting a maximum heap | > size (eg. -M512m) will cause GHC to try to trim down its memory use | > when it gets close to this boundary. | | Unfortunately neither of that helped. It appears that ghc simply | _needs_ that amount of memory. No matter what option I gave, at one | point it hit the 800 MB limit and aborted. (I specified -M800 because | if it used more memory than that, the machine stood basically still | with thrashing.) | | Looks like I'll have to support the memor chip industry ... The | problem is that if a 512MB machine cannot compile it, I wonder how the | _users_ of my program will get along. I guess they'll tend to have | smaller machines than the average software developer does. | | -peter | _______________________________________________ | Glasgow-haskell-users mailing list | Glasgow-haskell-users@haskell.org | http://www.haskell.org/mailman/listinfo/glasgow-haskell-users