Performance issue
sol opened this issue · comments
@runeksvendsen this looks bad, but hopefully easy to fix. Can you help with adding a minimal self-contained example that demonstrates the issue?
I just did a couple of test with the example given in the tasty readme and couldn't see any performance difference between hspec
and tasty
.
What I noticed though is that for some reason ghci
is about twice as fast as compiled (regardless of optimization level).
I will see if I can deduce a proper, minimal example.
Lessons so far: it's not shouldBe
vs ==
(makes no difference if I switch out shouldBe
with ==
).
Possible clue: are Hspec and Tasty handling depth in the same way? In other words, does defaultConfig { configSmallCheckDepth = <depth> }
for Hspec has the same effect as localOption (SC.SmallCheckDepth <depth>)
for Tasty?