Parallel --make (GHC build times on newer MacBook Pros?)
nominolo at googlemail.com
Tue Aug 30 01:42:27 CEST 2011
The performance problem was due to the use of unsafePerformIO or other
thunk-locking functions. The problem was that such functions can
cause severe performance problems when using a deep stack. The
problem is that these functions need to traverse the stack to
atomically claim thunks that might be under evaluation by multiple
The latest version of GHC should no longer have this problem (or not
as severely) because the stack is now split into chunks (see  for
performance tuning options) only one of which needs to be scanned.
So, it might be worth a try to re-apply that thread-safety patch.
On 29 August 2011 21:50, Max Bolingbroke <batterseapower at hotmail.com> wrote:
> On 27 August 2011 09:00, Evan Laforge <qdunkan at gmail.com> wrote:
>> Right, that's probably the one I mentioned. And I think he was trying
>> to parallelize ghc internally, so even compiling one file could
>> parallelize. That would be cool and all, but seems like a lot of work
>> compared to just parallelizing at the file level, as make would do.
> It was Thomas Schilling, and he wasn't trying to parallelise the
> compilation of a single file. He was just trying to make access to the
> various bits of shared state GHC uses thread safe. This mostly worked
> but caused an unacceptable performance penalty to single-threaded
> Glasgow-haskell-users mailing list
> Glasgow-haskell-users at haskell.org
Push the envelope. Watch it bend.
More information about the Glasgow-haskell-users