1536479 - Babel compile should not have a performance penalty

Status: NEW

(DevTools :: Debugger, task, P3)

Description

[Jason Laster [:jlast]]

Currently there is a per-directory cost for compiling, it would be nice if the performance were linear w/ respect to babel and not Node Startup time.

Comment 1

[Logan Smyth [:loganfsmyth]]

As an intermediate step, I wonder if it would be worth considering https://www.npmjs.com/package/v8-compile-cache as a means to avoid recompiling the Babel file every time node runs?

Comment 2

[Jason Laster [:jlast]]

v8 snapshots are enabled in node 12.5.0, seems likely a good way to speed up builds once we're willing to jump to node 12.5.0 https://github.com/nodejs/node/issues/17058#issuecomment-506381198

• NPM library available now https://www.npmjs.com/package/v8-compile-cache

Comment 3

[Alexandre Poirot [:ochameau]]

Note that babel is one thing, but that wouldn't get rid of node execution overhead.

Comment 4

[Jason Laster [:jlast]]

That is reasonable. I think V8 snapshots might do that though. https://github.com/nodejs/node/issues/17058#issuecomment-506381198

Comment 5

[Dan Mosedale (:dmosedale, :dmose)]

In general, it looks like V8 snapshots appear to help a bit now, and there's a bunch of headroom to win more: https://github.com/nodejs/node/issues/17058#issuecomment-508596356

Comment 6

[Dan Mosedale (:dmosedale, :dmose)]

Bug 1461714 was where this build strategy was first implemented, so linking there for reference.