Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Streamed response processing performance improvements #2645
That was interesting. The problem here was that headers are sent out before materialization but that didn't take into account that I might want to also handle errors during materialization with an error response. I now moved sending out headers into the substream.
…slow When the future is successful it will always create a `NoSuchElementException` including stack trace.
It turned out that aside from materialization which is still somewhat slow at least some bits of slowness were transferred from materialization to building stream graphs. The culprit in this case is `Source.concat`, which is really slow.