On Fri, Apr 21, 2017 at 11:21 AM, Johannes Rieken 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 stor
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
mac
Thanks for clarifying!
On Friday, April 21, 2017 at 10:00:03 AM UTC+2, Ben Noordhuis wrote:
>
> On Fri, Apr 21, 2017 at 9:51 AM, Johannes Rieken
> > wrote:
> > Does the data depend on things like endian-ness, CPU etc or only
> > on v8-locals like v8-version and v8-flags?
>
> All of the above;
As Ben says: The code cache is specific the exact source string, the CPU
(cpu family & cpu flags, e.g. whether certain features are supported), the
exact V8 version (since there is no mechanism to guarantee correctness
across versions), and the compile options (debug, release, certain features
that
On Fri, Apr 21, 2017 at 9:51 AM, Johannes Rieken
wrote:
> Does the data depend on things like endian-ness, CPU etc or only
> on v8-locals like v8-version and v8-flags?
All of the above; it's machine-, version- and invocation-specific.
--
--
v8-users mailing list
v8-users@googlegroups.com
http:
We have a large chunk of (minified and bundled) code and I am using `
kProduceCodeCache` and `kConsumeCodeCache` to improve startup performance.
I understand that cached data is rejected when the source changes but I
wonder what else can cause this? I am especially interested if I can create
ca
