I’ve found that if I’m using scala.concurrent.Future in my code, I can get some really easy performance gains by just switching to scalaz.concurrent.Task instead, particularly if I’m chaining them with map or flatMap calls, or with for comprehensions. Jumping into thread pools Every Future is basically some work that needs to be submitted to a thread pool. When you call futureA.flatMap(a => future
![Easy Performance Wins With Scalaz - Higher Order](https://cdn-ak-scissors.b.st-hatena.com/image/square/35c2ef22027462369ede3597410d0d6299923236/height=288;version=1;width=512/http%3A%2F%2Fblog.higher-order.com%2Fimages%2Ffuturetaskplot.png)