Emit build output without EntrypointsOperation
`emit_all_output_assets_once_with_issues_operation` wrapped the emit operation in `EntrypointsOperation::new`, only to discard the resulting entrypoints. That created one `pick_endpoint` root operation per endpoint (~6,000 in a large app), each becoming a new aggregation upper of the whole emit graph and copying its collectibles. In `bench/nested-deps-app-router-many-pages` at 32 CPUs this kept the end of the emit phase at ~4.5 busy cores. Read the emit operation directly instead. The issues and effects are still collected from the same operation. On canary 8521c6ae, 32 CPUs, 4 interleaved rounds, median paired change vs. canary: turbopack-emit -62.3% (12.3 s -> 4.5 s), "Compiled in" -19.1%, wall -15.1%. `.next` output and build issues are unchanged. Co-authored-by:Tobias Koppers <1365881+sokra@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment