#3061: GHC's GC default heap growth strategy is not as good as other runtimes
--------------------------------------+-------------------------------------
Reporter: dons | Owner:
Type: bug | Status: closed
Priority: normal | Milestone: 6.12 branch
Component: Runtime System | Version: 6.10.1
Resolution: fixed | Keywords: performance, GC
Difficulty: Unknown | Os: Unknown/Multiple
Testcase: yes | Architecture: Unknown/Multiple
Failure: Runtime performance bug |
--------------------------------------+-------------------------------------
Changes (by john435):
* status: new => closed
* resolution: => fixed
Comment:
Replying to [comment:1 simonmar]:
> So you're not allowed to use GC settings in the shootout? I think this
benchmark is pathological for our default GC settings. The reason is that
we use a small fixed-size allocation area, which is usually good for cache
behaviour, but in this benchmark when we get to the larger tree sizes, we
always GC before the tree has been constructed, and the GC therefore has
to copy [http://treatmentofmesothelioma.org/mesothelioma.html
mesothelioma] the tree, possibly multiple times. In fact this is very
similar to a standard GC benchmark that we use.
>
> I'd be quite interested to know what
[http://healthyweightlosspills.com/healthy weight loss] other runtimes
do here. I played a little with scaling up the size of the allocation
area if we find we're copying a lot, but didn't see a dramatic
improvement.
Thank you for your answer.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3061#comment:7>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
