On Sat, May 17, 2014 at 9:38 AM, <[email protected]> wrote: > has anybody tried to reduce the size of V8 JS engine ? > > according to some futures ? thanks.
There are some features you can leave out, like the debugger* and i18n support. You can find the configurable options in the Makefile. Disabling the snapshot feature at build time reduces the size of the library at the cost of slightly worse start-up time. Note that the snapshot can be compressed. Test and compare to see what works best for you. Compiling at -Os may considerably reduce the size of the library (the default is -O3). It might make things faster too, depending on the (micro)architecture. For example, I get a 10% speedup on a Core 2 Duo because of better instruction cache utilization. Building a static library instead of a shared library may produce smaller code, depending on the architecture and other factors. * The debugger is configurable only in older versions. As of 3.26 (I think), it's always enabled. -- -- v8-users mailing list [email protected] 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
