Updates:
Status: WorkingAsIntended
Comment #2 on issue 3950 by [email protected]: Compile Javascript
asynchronously
https://code.google.com/p/v8/issues/detail?id=3950
First off, 2014 was last year, not last month. The blog post talks about
backgrounding most of the optimization work that the optimizing compiler is
doing; this is unrelated to startup (as Ben has already explained in the
io.js issue).
There's some work being done to start parsing before the source is complete
transferred over the network; however for server-side JS that's probably
not relevant.
There's also some recent work to allow caching of compiled code. This is
something that the embedder needs to support; Chrome already does.
Asynchronous non-optimized compilation won't happen any time soon for
architectural reasons (it's effectively impossible, and I'm not even sure
how much you'd have to rewrite to make it possible).
When implementing your own lazy-loading scheme, be careful not to defeat
any optimizations that the system (V8 + embedder) is already doing. When in
doubt, measure the benefit (and maybe re-measure every year or so). I would
expect that a server starts up rarely and then runs for a long time, so
initialization latency shouldn't be much of an issue in this case.
I don't think this bug adds any value or information; closing.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" 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.
