On Sat, Oct 21, 2017 at 8:28 AM, Vaibhav Pande <[email protected]> wrote: > From what I have seen till now the there is a thread pool created which > waits on the DefaultPlatform::queue_ and a task is popped by taking a > lock(work sharing).
That's the default Platform implementation; embedders like Chromium and Node.js can (and do) replace it. Node.js did use it for quite some time but no longer. > What I am not sure of is what type of tasks are present in the queue > mentioned above and from where are the tasks coming in ? > As per my knowledge the tasks are both compilation and heap management > tasks. Can someone please verify this and tell me if this is right? Yes, the main two are concurrent recompilation and concurrent marking (i.e., garbage collection.) > Also, is there any design document available for knowing the V8's threading > policy as I want to see if I can change the work sharing as present to work > stealing(http://supertech.csail.mit.edu/papers/steal.pdf) but before > starting up, I would want to know if it would be useful or not. I believe DefaultPlatform is mainly intended as a convenience, to get up and running quickly. Since it's often swapped out by embedders, improvements aren't going to make a major impact. -- -- 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.
