We've actually been working on reducing memory overhead around the snapshot, see the lazy builtins design doc at http://goo.gl/dxkYDZ. Note though that this is intended to reduce runtime memory use, not the size of the snapshot blob itself. I'd expect the snapshot blob to grow further in the future.
As Ben says below, it's possible to build V8 without a snapshot, but startup costs will increase significantly. May I ask what your main concern is? Runtime memory consumption or binary size? On Thu, Dec 14, 2017 at 10:14 AM, Ben Noordhuis <i...@bnoordhuis.nl> wrote: > On Thu, Dec 14, 2017 at 7:22 AM, <uzair.jal...@samsung.com> wrote: > > 1) How is snapshot_blob.bin generated at compile time ? (If possible > where > > in chromium code ) > > Look for a file called mksnapshot.cc in v8/src/snapshot. > > > 2) Is it possible to reduce the size of snapshot_blob.bin ? (if yes > where in > > chromium code do we do it and will it have any performance regression ?) > > You could disable internationalization (v8_enable_i18n_support=0) but > that's about it. It won't affect performance but the Intl JS object > will have only bare-bones functionality. > > You can disable the snapshot entirely (v8_use_snapshot=0) but that > does have a performance impact because it shifts the cost of > construction to Context::New(). Expect that function to slow down by > 5-10x. -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
