fused-effects 1.1 performance degradation? about fused-effects HOT 6 OPEN

This is very interesting. I’m going to see if I can reproduce in https://github.com/patrickt/effects-benchmarks.

from fused-effects.

I don’t think we observed any performance degradation in our internal app, but I could be wrong, and that’s a very different workload.

from fused-effects.

Haven’t observed it in effects-benchmarks. Going to try the bench folder here and see if that reveals something. Perhaps INLINE stuff is coming into play, or this is an instance of criterion’s timing issues (we prefer gauge).

from fused-effects.

Hmm, can’t reproduce this in the benchmark suite either.
With 1.0: https://gist.github.com/patrickt/ac727d6e5ca9ee557c5b6ccb7115e26b
With 1.1: https://gist.github.com/patrickt/7beb3f075b04d3fc15f39b238666bc41

from fused-effects.

Hmm interesting. 'file sizes' and 'reinterpretation' do show the expected improvement. Perhaps 'big stack' and 'countdown' are hitting some edge case that is now slower.

BTW I cleaned up the diff between the 2 branches AlistairB/effect-zoo@removed-eff...fused-1.1

from fused-effects.

Hella cool work @AlistairB, thank you so much for doing this and sharing your results with us!

I’m not seeing a smoking gun here; since this isn’t using any of our carriers that I can see, the only real change seems to be the difference in alg’s signature between the two versions, which I’d expect to be a net null or even slight win for 1.1 given that we no longer need to (re)construct effects via Effect (and thus should enjoy fewer allocations overall).

It’s definitely possible that we’re more sensitive to inlining now, or that we’ve underestimated the cost of constructing operations with send in the new model; hopefully we can quantify where these costs are coming from a little more precisely.

Either way, thank you again!

from fused-effects.