next.js

terribleplan/next.js

Fork 0

mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00

Commit graph

Author	SHA1	Message	Date
Tim Neutkens	32451e979e	Move out requires from renderToHTML (#5915 ) This brings us one step closer to outputting serverless functions as renderToHTML now renders the passed components, which allows us to bundle the renderToHTML function together with statically imported components in webpack.	2018-12-18 17:12:49 +01:00
Benjamin Kniffler	e6c3686629	multi-threaded export with nice progress indication (#5870 ) This PR will - allow nextjs export to use all available CPU cores for rendering & writing pages by using child_process - make use of async-sema to allow each thread to concurrently write multiple paths - show a fancy progress bar while processing pages (with non-TTY fallback for CI web consoles) The performance gain for my MacBook with 4 CPU cores went from ~25 pages per second to ~75 pages per second. Beefy CI machines with lots of cores should profit even more.	2018-12-12 13:59:11 +01:00

Author

SHA1

Message

Date

Tim Neutkens

32451e979e

Move out requires from renderToHTML (#5915 )

This brings us one step closer to outputting serverless functions as renderToHTML now renders the passed components, which allows us to bundle the renderToHTML function together with statically imported components in webpack.

2018-12-18 17:12:49 +01:00

Benjamin Kniffler

e6c3686629

multi-threaded export with nice progress indication (#5870 )

This PR will

- allow nextjs export to use all available CPU cores for rendering & writing pages by using child_process
- make use of async-sema to allow each thread to concurrently write multiple paths
- show a fancy progress bar while processing pages (with non-TTY fallback for CI web consoles)

The performance gain for my MacBook with 4 CPU cores went from ~25 pages per second to ~75 pages per second. Beefy CI machines with lots of cores should profit even more.

2018-12-12 13:59:11 +01:00

2 commits