Personal tools

Benchmarks Game/Parallel/Knucleotide

From HaskellWiki

< Benchmarks Game | Parallel(Difference between revisions)
Jump to: navigation, search
(created page, asked about threading)
 
Line 1: Line 1:
 
K-Nucleotide is currently the worst performing Haskell/ghc entry, by a good margin (16 times slower than the leader, vs. 6 times for the next worst).
 
K-Nucleotide is currently the worst performing Haskell/ghc entry, by a good margin (16 times slower than the leader, vs. 6 times for the next worst).
 
Several of the leading entries for multi-core k-nucleotide explicitly manipulate threads, while the Haskell/ghc entries do not. Is this a case of no one's gotten around to doing this, or is there another reason?
 
Several of the leading entries for multi-core k-nucleotide explicitly manipulate threads, while the Haskell/ghc entries do not. Is this a case of no one's gotten around to doing this, or is there another reason?
  +
:: No one's gotten around to it. Please enter a submission!

Revision as of 22:56, 8 December 2008

K-Nucleotide is currently the worst performing Haskell/ghc entry, by a good margin (16 times slower than the leader, vs. 6 times for the next worst). Several of the leading entries for multi-core k-nucleotide explicitly manipulate threads, while the Haskell/ghc entries do not. Is this a case of no one's gotten around to doing this, or is there another reason?

No one's gotten around to it. Please enter a submission!