[GHC] #8732: Global big object heap allocator lock causes contention
GHC
ghc-devs at haskell.org
Tue Feb 3 02:01:11 UTC 2015
#8732: Global big object heap allocator lock causes contention
-------------------------------------+-------------------------------------
Reporter: tibbe | Owner: simonmar
Type: bug | Status: new
Priority: normal | Milestone: 7.12.1
Component: Runtime System | Version: 7.6.3
Resolution: | Keywords:
Operating System: Unknown/Multiple | Architecture:
Type of failure: Runtime | Unknown/Multiple
performance bug | Test Case:
Blocked By: | Blocking:
Related Tickets: | Differential Revisions:
-------------------------------------+-------------------------------------
Comment (by tibbe):
What about the idea of just using malloc? Modern mallocs like TCMalloc are
already multithreaded and seem to just deal with all the annoying issues.
Gregory Collins said that in Snap they just don't use the "built-in"
ByteString construction functions and instead just call malloc.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8732#comment:15>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list