as fast as possible implies spending the resources that way.

Going close to as fast as possible while saving a stream for the other approaches makes sense as an approach, but let's not ignore that there's a compromise/tradeoff here. Might not matter in orgs with near infinite resources