Re: [v8-users] Re: Isolate Creation Times

2017-02-23 Thread Jochen Eisinger 
Hey

That sounds odd. Could you file a bug at crbug.com/v8/new and provide the
gn args you used for building?

Thanks
Jochen

Brendan Bates  schrieb am Do., 23. Feb. 2017,
18:07:

> I should also note that I can replicate this by simply running the d8
> executable, which seems to take about 5 seconds to bootstrap.
>
>
> On Thursday, February 23, 2017 at 10:59:47 AM UTC-5, Brendan Bates wrote:
>
> I'm posting here to see if anyone has experienced this recently.
>
> We upgraded our scripting environment from *5.1.281.65 *to *5.7.492.44*.
> Everything as far as building with GN has gone
> smoothly, however one odd issue is with the timing of the isolate creation:
>
>
> _isolate = Isolate::New(createParams);
>
>
> This used to be nearly instantaneous (few ms at most), now it's taking
> about 5 seconds on my Windows 10 64-bit
> environment (with a 32-bit build).  The allocator in the createParams is
> using the default v8 allocator.  Will using an
> empty snapshop help?  If we have 20 scripts loaded, that's 100 seconds of
> startup time... way too much.  Any help
> would be appreciated.  Thanks!
>
> --
> --
> 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.
>

-- 
-- 
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.

[v8-users] Re: Isolate Creation Times

2017-02-23 Thread Brendan Bates 
I should also note that I can replicate this by simply running the d8 
executable, which seems to take about 5 seconds to bootstrap.

On Thursday, February 23, 2017 at 10:59:47 AM UTC-5, Brendan Bates wrote:
>
> I'm posting here to see if anyone has experienced this recently.
>
> We upgraded our scripting environment from *5.1.281.65 *to *5.7.492.44*. 
>  Everything as far as building with GN has gone 
> smoothly, however one odd issue is with the timing of the isolate creation:
>
>
> _isolate = Isolate::New(createParams);
>
>
> This used to be nearly instantaneous (few ms at most), now it's taking 
> about 5 seconds on my Windows 10 64-bit 
> environment (with a 32-bit build).  The allocator in the createParams is 
> using the default v8 allocator.  Will using an
> empty snapshop help?  If we have 20 scripts loaded, that's 100 seconds of 
> startup time... way too much.  Any help
> would be appreciated.  Thanks!
>

-- 
-- 
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.

[v8-users] Isolate Creation Times

2017-02-23 Thread Brendan Bates 
I'm posting here to see if anyone has experienced this recently.

We upgraded our scripting environment from *5.1.281.65 *to *5.7.492.44*. 
 Everything as far as building with GN has gone 
smoothly, however one odd issue is with the timing of the isolate creation:


_isolate = Isolate::New(createParams);


This used to be nearly instantaneous (few ms at most), now it's taking 
about 5 seconds on my Windows 10 64-bit 
environment (with a 32-bit build).  The allocator in the createParams is 
using the default v8 allocator.  Will using an
empty snapshop help?  If we have 20 scripts loaded, that's 100 seconds of 
startup time... way too much.  Any help
would be appreciated.  Thanks!

-- 
-- 
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.

[v8-users] PSA: V8 is going to switch to a new compiler architecture after 5.8 branch cut

2017-02-23 Thread Michael Hablich 
Summary

The V8 team is currently working on a new compiler pipeline that will help
us bring future speedups to real-world JavaScript
.
In the next few weeks we will replace our current compiler architecture
based on a non-optimizing (FullCodeGen) and optimizing compiler
(Crankshaft) pair with the combination of an interpreter (Ignition) and a
new optimizing compiler (TurboFan).

You can try the new pipeline by setting an about:flags entry
 or
passing the flag "--future" to d8.
Eng contact emails

da...@chromium.org, bmeu...@chromium.org (TurboFan), rmcil...@chromium.org
(Ignition)
Design docs

TurboFan: https://github.com/v8/v8/wiki/TurboFan
Ignition: https://github.com/v8/v8/wiki/Interpreter
Planned date for the switch

March 2017.
Affected platforms

All
How to try the new architecture

This dedicated blog
 post
describes how the new pipeline can be switched on.
Debuggability

DevTools support is the same as with the classic pipeline.
Interoperability and Compatibility Risk

There are no user-facing changes (e.g. no new APIs changed). The new
pipeline will change V8's performance profile considerably. Real-world
JavaScript performance

should improve and V8 memory consumption should be reduced. We expect
controlled regressions in some synthetic JavaScript benchmarks like Octane.
We plan to purposefully address selected regressions in upcoming releases.

We are already A/B testing the new pipeline to Canary and Dev channel in
M58. Please note that individually, Ignition (on low memory devices and for
certain JavaScript features on all platforms) and TurboFan (for certain
JavaScript features) have been active for a long time (> half a year).
Additionally we have set-up dedicated tests for security, correctness,
performance and stability.
How to report bugs

As this is a major change in V8 we anticipate that unexpected, negative
side-effects in performance, memory profile, security or correctness might
occur. If you see anything, please feel encouraged to report a bug

.

If you have any concerns or remarks, please feel free to simply respond to
this thread or send a mail directly to habl...@chromium.org

Cheers,

Michael

-- 
-- 
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.