V8 supports "snapshots" where the V8 heap can be serialized and stored. A V8 instance can then be started right of this serialized heap. In Chromium this is used to reduce startup time. As parts of V8 is implemented in JavaScript time is spend in V8 startup compiling this builtin JavaScript which (together with other heap initialization) is avoided when starting V8 off a snapshot. The snapshot does not need to be taken just after normal initialization is done as is the case for Chromium (and V8 built using the snapshot=on option to the SCons build). It can be taken at any point in time e.g. after loading common JavaScript code used by a embedding application. Note however that this is a "one shot operation" where the full heap is loaded from the snapshot there is currently no support in V8 for "partial" snapshots.
Regards, Søren On Wed, Aug 5, 2009 at 23:01, ionlupascu <ionlupa...@gmail.com> wrote: > > Hello all, > Is possible following variants: > 1. Compile v8 code, save in binary file specific by os and platform > and after then run this binary file as a program. > 2. Or compile v8 code by c++ application, save compiled data in file > or anywhere, load compiled code and after then run this code in this c+ > + application? > > Thanks in advance. > > > --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
