On Fri, Apr 21, 2017 at 11:21 AM, Johannes Rieken <[email protected] > wrote:
> For some background: We are using cached data since a while in VS Code and > are quite happy with it. It's one of the simpler things to improve start up > time. The only downside is the slow down on first start when we generate > and store the cached data and I was thinking about making our build > machines do this. > You could also try the startup snapshot: This is similar to the code cache (in fact, the code cache implementation was derived from the startup snapshot). This is a build-time operation. It caches more code (that is, it compiles everything), and it runs the code generator so that code will be potentially less efficient, but independent of the cpu feature flags (that is, specialised to a CPU family; not to a particular model). The JS source + V8 source mismatch issue is auto-magically solved by being bundled with the binary. This is used by Chrome to speed up browser + tab startup. (This isn't super well document, though. See v8_extra_library_files in BUILD.gn.) An alternative, that would also work with code cache: Chrome Android has a similar problem. We discussed not running with snapshot/code cache, and then compiling (in idle time) the snapshot/code cache in a separate & "clean" process. That way, you can hide the cache generation time. You'd still have the initial unaided & somewhat slower startup. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
