you're doing it wrong: haskell is too slow.
doing it in go and then using cgo where necessary will get you pretty close to C speed.
Conspicuously you don't address Haskell at all. Then again, who cares what might actually be best for OP? There's an advocacy bingo card in play!
Our platform is fast and could be used for some slower strategies. If we replaced pieces of it with C we could be competitive but probably never less then 10 microseconds wire to wire.