Difference between revisions of "Benchmarks Game/Parallel"
Jump to navigation
Jump to search
DonStewart (talk | contribs) |
DonStewart (talk | contribs) |
||
Line 4: | Line 4: | ||
== Advice == |
== Advice == |
||
− | * Check the GC stats with +RTS -sstderr -RTS, if that number if over 5%, |
+ | * Check the GC stats with +RTS -sstderr -RTS, if that number if over 5%, use -AxxxM to set a better default heap size. |
− | use -AxxxM to set a better default heap size. |
||
* Use N+1 capabilities for SMP, e.g. +RTS -N5 -RTS, for the quad core. |
* Use N+1 capabilities for SMP, e.g. +RTS -N5 -RTS, for the quad core. |
||
* Take the single threaded, fast programs and parallise them |
* Take the single threaded, fast programs and parallise them |
||
Line 12: | Line 11: | ||
== Programs == |
== Programs == |
||
− | * [/BinaryTrees] |
+ | * [[/BinaryTrees]] |
Revision as of 22:20, 1 September 2008
Quad-core enabled parallel Haskell benchmark entries, for the 64 bit quad core shootout.
Advice
- Check the GC stats with +RTS -sstderr -RTS, if that number if over 5%, use -AxxxM to set a better default heap size.
- Use N+1 capabilities for SMP, e.g. +RTS -N5 -RTS, for the quad core.
- Take the single threaded, fast programs and parallise them
- Parallel strategies are the lightest way to add SMP capabilities.