discuss Digest, Vol 126, Issue 8

[Mani Sarkar]

That sounds awesome.

Thanks for sharing this with us.

Cheers
Mani

On Tue, 10 Oct 2017 12:57 , <discuss-request at openjdk.java.net> wrote:

> Send discuss mailing list submissions to
>         discuss at openjdk.java.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mail.openjdk.java.net/mailman/listinfo/discuss
> or, via email, send a message with subject or body 'help' to
>         discuss-request at openjdk.java.net
>
> You can reach the person managing the list at
>         discuss-owner at openjdk.java.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of discuss digest..."
>
>
> Today's Topics:
>
>    1. Re: Call for Discussion: New Project: Loom
>       (=?UTF-8?B?5p2O5LiJ57qiKOS4iee6oik=?=)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 09 Oct 2017 20:26:18 +0800
> From: "=?UTF-8?B?5p2O5LiJ57qiKOS4iee6oik=?="
>         <sanhong.lsh at alibaba-inc.com>
> To: <ron.pressler at oracle.com>,  <discuss at openjdk.java.net>
> Subject: Re: Call for Discussion: New Project: Loom
> Message-ID: <012d01d340f9$ceeae010$6cc0a030$@alibaba-inc.com>
> Content-Type: text/plain;       charset="gb2312"
>
> Hi Ron,
>
> I are  very excited about this proposal to add lightweight threads  to
> Java.
>
>
>
>
> As I have talked at JVMLS [1], our own customized OpenJDK version has
> implemented  some similar mechanism proposed by loom(we called this as Wisp
> internally),  which is already widely deployed in Alibaba production
> environment.  A couple of core ecommerce applications (running in very
> large
> scale cluster) are running on top of Wisp. By this way, we achieved 10+%
> CPU saving, lots of thread context switches could be reduced by
> transferring
> from thread to coroutine.
>
>
>
> More specifically,  our implementation is relying on the continuation
> primitive support made by  [2] , which is part of MLVM project. Moreover,
> we added our own scheduler(fully written in Java) to support coroutine
> yielding at almost all possibly blocked places in OpenJDK, including:
>
> -        Java  synchronization(compiled & runtime code change)
>
> -        J.U.C
>
> -        Java network IO
>
> -        Java disk IO
>
> Our goal is to allow Java developers to write in synchronous but gain
> performance of asynchronous for free, they just change a couple of line of
> code and do some parameter configuration, the control transferring between
> coroutines is totally handled by underlying  JDK transparently.
>
>
>
> We are interested in contributing to this project.
>
>
>
> [1]:
>
> https://www.slideshare.net/sherrylso/optimizing-jvm-at-alibaba-for-ecommerce
> -apps-running-on-100000-servers
> <https://www.slideshare.net/sherrylso/optimizing-jvm-at-alibaba-for-ecommerce-apps-running-on-100000-servers>
>
> [2]:
>
> http://hg.openjdk.java.net/mlvm/mlvm/hotspot/file/4cd7d914b0e3/coro-simple.p
> atch
>
>
>
> End of discuss Digest, Vol 126, Issue 8
> ***************************************
>
-- 
@theNeomatrix369 <http://twitter.com/theNeomatrix369>*  |  **Blog
<http://neomatrix369.wordpress.com/>**  |  *@adoptopenjdk | Dev communities
*Meet-a-Project - *MutabilityDetector
<https://github.com/MutabilityDetector>*  |  **Bitbucket
<https://bitbucket.org/neomatrix369>* * |  **Github
<https://github.com/neomatrix369>* * |  **LinkedIn
<http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>*
*Come to Devoxx UK 2018:* http://www.devoxx.co.uk/

*Don't chase success, rather aim for "Excellence", and success will come
chasing after you!*