[Webkit-unassigned] [Bug 174276] JSC should support threads in JS

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=174276

--- Comment #7 from Asmithdev <austin at asmithdev.com> ---
Perhaps you misunderstood what I was saying as I am already using workers as threads, it would be wise to do more research in how to communicate between workers today. 

Workers are "threads" and they rely on an underlying message passing interface, atomic operations allow for a shares state and locking, the spec has been publicly available for several years and they will allow a reduction in the amount of data that is moved (serialized) between threads.

Not referencing the most popular JavaScript parallel execution library or any of the other ones that are out there seems like an intentional attempt to muddy the waters as to what options are currently available. 

The childish response is unfortunately par for the course with what I anticipated given the previous lack of references to current JavaScript multithreading/concurrent/parallel execution libraries.

I personally have plenty of experience using things like sidekiq as referenced in the pdf linked later in the article and even the developers of sidekiq clearly warn about it's limitations especially with multiple queues.

"I don't recommend having more than a handful of queues. Lots of queues makes for a more complex system and Sidekiq Pro cannot reliably handle multiple queues without polling. M Sidekiq Pro processes polling N queues means O(M*N) operations per second slamming Redis."

I am not sure why this would have been a referenced program in the first place as it doesn't relate to JavaScript at all.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170901/5c2689f2/attachment.html>