Thanks. Just to put this in perspective to cached-data. Warm snapshots with compiled JS code can be distributed across different machines, CPU-architecture and helps with the very first startup but cached data is more efficient because it can use system specific tricks. Is that a somewhat correct description of both?
Cheers, Joh On Wednesday, June 21, 2017 at 4:42:10 PM UTC+2, Yang Guo wrote: > > mksnapshot does not by default include any code generated from JavaScript > to save space. Please take a look at test/cctest/test-serialize.cc on > examples on how to use WarmUpSnapshotBlob. You can also dive deeper and > look at its implementation, which uses the more powerful SnapshotCreator. > > Cheers, > > Yang > > On Wed, Jun 21, 2017, 08:28 <[email protected] <javascript:>> wrote: > >> My understanding is that V8 puts generated and optimised code for my >> functions onto the heap. Now, how does this relate to heap snapshots? Is >> code generated by v8 part of snapshots and is the purpose of the >> warmup-script in mksnapshot to run my function often enough to be hot and >> optimised? Thanks in advance. >> >> -- >> -- >> v8-dev mailing list >> [email protected] <javascript:> >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- -- 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.
