# What happened to Fusing.aggressive()?
**URL:** https://discuss.akka.io/t/what-happened-to-fusing-aggressive/1604
**Category:** Akka Streams & Alpakka
**Tags:** streams
**Created:** [July 18, 2018, 7:36pm UTC](https://discuss.akka.io/t/what-happened-to-fusing-aggressive/1604 "2018-07-18T19:36:01Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@jamie.phelps](https://discuss.akka.io/u/jamie.phelps)
#### Post date: [July 18, 2018, 7:36pm UTC](https://discuss.akka.io/t/what-happened-to-fusing-aggressive/1604/1 "2018-07-18T19:36:01Z")
I’ve come across comments online and in older akka docs re: Fusing.aggressive() and how that may help reduce materialization costs in, for example, a web service gateway application that materializes a new stream for every request. However, it appears that class is no longer in akka 2.5.+.
Have the auto-fusing costs during materialization been improved since then to make that pre-materialization fusing no longer of any benefit?
thanks
---
### Author:  [@johanandren](https://discuss.akka.io/u/johanandren)
#### Post date: [July 19, 2018, 8:00am UTC](https://discuss.akka.io/t/what-happened-to-fusing-aggressive/1604/2 "2018-07-19T08:00:44Z")
Having a separate fusing operation was very much an artifact of how the old materializer was designed. The redesigned materializer (`PhasedFusingActorMaterializer`, completed spring 2017), also encompass how the streams are laid out, tries to make as much of the work already being done when constructing the graph.
I don’t have any numbers on hand for the improvements, I remember them as substantial though. They could be checked by running the materialization benchmarks in the akka-jmh-bench on 2.5 and 2.4 respectively if you want to dig into it.