[concurrency-interest] OpenJDK Project Loom - lightweight threads for Java

Dávid Karnok akarnokd at gmail.com
Wed Oct 25 15:58:18 EDT 2017


I'm a bit worried about the performance implications in exchange for the
promise of imperative looking code.

For example, having a bounded blocking queue suspend on being full/empty.
If the producer runs too fast, it gets suspended all the time with what it
seems to be quite a lot of state to be saved and restored in a thread-safe
manner. Similarly, a fast running consumer would get suspended all the time.


2017-10-25 21:40 GMT+02:00 thurstonn <thurston at nomagicsoftware.com>:

> Joshua Bloch wrote
> > This is very similar in spirit to the "many-to-few" threading model that
> > was popular in the '90s. You can read about it in Butenhof's *Programming
> > with POSIX Threads (Addison-Wesley, 1997)*, §5.6.3. The concept pretty
> > much
> > died on the vine when kernel threads got faster and cheaper, but
> > everything
> > old is new again.
>
> Uh, Erlang
>
>
>
>
> --
> Sent from: http://jsr166-concurrency.10961.n7.nabble.com/
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest
>



-- 
Best regards,
David Karnok
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20171025/3aafb611/attachment.html>


More information about the Concurrency-interest mailing list