|
Re: ghc releasing memory during compilation: msg#00069lang.haskell.glasgow.bugs
Duncan Coutts wrote: As some are aware some Wash modules cause ghc to take a very large No, not at the moment. One thing we planned to do but never got around to is to use madvise() to improve swapping behaviour when memory is tight (see the thread that Bulat refferred to). In this case if it can do so, it should be quite dramatic. It'd ought to Yes it ought to. A related problem is that the block allocator is really stupid. It makes no attempt to reduce fragmentation, and in fact freeing blocks is O(n) because the freelist is kept sorted in address order. This isn't usually an issue, although it has been reported to be noticeable with very large residencies (500M+). It's on my list to fix at some point. I mention this because freeing all that memory might not be possible if it is highly fragmented. Cheers, Simon
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: ghc releasing memory during compilation, Simon Marlow |
|---|---|
| Next by Date: | Re: ghc releasing memory during compilation, Duncan Coutts |
| Previous by Thread: | ghc releasing memory during compilation, Duncan Coutts |
| Next by Thread: | Re: ghc releasing memory during compilation, Duncan Coutts |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |