openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michele Sciabarra <mich...@sciabarra.com>
Subject Re: Proposal for "fixing" the Java Runtime
Date Mon, 07 Jan 2019 21:53:25 GMT
The slowdown in the init is because my PoC so far also compiles the source, I am sending a
.java not a .jar. My plan is to implement also the precompilation as in Go.

-- 
  Michele Sciabarra
  michele@sciabarra.com

----- Original message -----
From: David P Grove <groved@us.ibm.com>
To: dev@openwhisk.apache.org
Subject: Re: Proposal for "fixing" the Java Runtime
Date: Mon, 7 Jan 2019 16:35:01 -0500

Michele Sciabarra <michele@sciabarra.com> wrote on 01/07/2019 01:08:25 PM:
>
> I benchmarked the java runtime, here:
>
> https://sciabarracom.github.io/incubator-openwhisk-runtime-actionloop/
>
> As you can see the openwhisk/javaaction is pretty slow. Not sure
> why... So I did a proof of concept to see how much I can improve.
> Actually, a lot, as you can see the actionloop/java8, bringing the
> runtime on par with the others using action loop.
>
> The actionloop/java8 is only a PoC, it runs the hello.java but I did
> not run the tests. If the proposal is accepted I will work to make
> sue it passes all the tests of the current java runtime. Then I have
> in mind a lot of extensions,  supporting java 11, providing the
> ability to compile sources, download dependencies, compile also
> scala and kotlin...
>
> But let do things in order. It the community ok that I contribute an
> actionloop based java runtime?

Hi Michele,

	No objections to speeding up Java from me :)

	The gain in /run is impressive.  I do think we should try to
understand why there is a slowdown in /init and attempt to mitigate it
(since a cold start will do both /init and /run).


--dave

Mime
View raw message