wrongly posted
--
--
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
Is it related to meltdown and spectre?
--
--
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
nwjs claims to support web worker with node, allowing true threading. Each
thread gets its own javascript context and they don't share anything. They
only communicate with messages. The workers are entirely separate from
each other.
https://github.com/nwjs/nw.js/issues/494
I understand that updating object in shared memory need synchronization and
even with in-memory database task in general there will be a global lock
(not per-object because transaction will spread by different tables and
object) and only one process will write to memory so I think just global
lock
No, you cannot simply share all memory to get multi-threading. For
safely/correctly working with shared memory, you need
locking/synchronization primitives as well as certain guarantees in the
language's memory model. JavaScript is not designed for such purposes.
On Mon, Jan 8, 2018 at 3:52 PM
I don't know all details, I just a regular node developer who came up with
idea of "threading" in js and hope anybody with deep knowledge will clarify
some things. Javascript have old problem of lacking threading and all
advices of using multiple processes doesn't help because there are
I want to understand the reason behind acuire and release locks in j2v8
library
On Friday, January 31, 2014 at 2:21:38 PM UTC+5:30, Sara Abdelhameed wrote:
>
> Hello all,
> does v8 engine support multithreaded application ? and could I run two
> different javascript code in two different
