groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul King <pa...@asert.com.au>
Subject Re: GraalVM/Truffle ?
Date Thu, 14 Jun 2018 13:02:32 GMT
As it turns out, I haven't tried the indy artifacts/compilation switches as
yet, just the "classic/standard" jars. I'd suspect though that most benefit
would occur if targeting the GraalVM specifically when generating bytecode.

Cheers, Paul.

On Thu, Jun 14, 2018 at 10:42 PM Winnebeck, Jason <
Jason.Winnebeck@windstream.com> wrote:

> It’s interesting that it is slower, because I thought the point of it was
> to improve performance, especially regarding escape analysis and
> invokedynamic instruction? They’ve been publishing some very interesting
> benchmarks. The AOT mode is very interesting, too, especially if someone
> wanted to make some CLI commands in Groovy, although the resulting
> executables are still very large if you just wanted to make some shell
> “scripts” in Groovy. Though, I would suspect its AOT mode is not very
> compatible with Groovy due to extensive use of reflection.
>
>
>
> Jason
>
>
>
> *From:* Paul King [mailto:paulk@asert.com.au]
> *Sent:* Thursday, June 14, 2018 4:30 AM
> *To:* users@groovy.apache.org
> *Subject:* Re: GraalVM/Truffle ?
>
>
>
> Running numerous scripts on GraalVM worked fine for me and was only
> slightly slower in my tests than the standard Oracle JVM. I haven't done
> extensive testing though.
>
>
>
> As for actually leveraging any special GraalVM capabilities, I am not
> aware of any completed work/concrete plans to date.
>
>
>
> As for licensing, it may or may not be an issue. We'll have to see how
> things progress before we can say.
>
>
>
> Cheers, Paul.
>
>
>
>
>
> On Thu, Jun 14, 2018 at 1:33 AM MG <mgbiz@arscreat.com> wrote:
>
> Since GraalVM (https://en.wikipedia.org/wiki/GraalVM
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FGraalVM&data=02%7C01%7CJason.Winnebeck%40windstream.com%7Ce67a260963094d72ed7008d5d1d10f35%7C2567b4c1b0ed40f5aee358d7c5f3e2b2%7C1%7C0%7C636645618198046382&sdata=oRUQ9fKzVaQXVOfwFCvleWQIbsWWWh1uIoSuaJCOfaI%3D&reserved=0>)
> was mentioned here
> recently: Do we have any statement on plans of Groovy with regards to
> GraalVM, including Truffle ? It might be good to have an official
> statement here on the main Groovy page and on Wikipedia
> (https://en.wikipedia.org/wiki/Apache_Groovy
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FApache_Groovy&data=02%7C01%7CJason.Winnebeck%40windstream.com%7Ce67a260963094d72ed7008d5d1d10f35%7C2567b4c1b0ed40f5aee358d7c5f3e2b2%7C1%7C0%7C636645618198056394&sdata=THXlJXbqPZTA5td46Ore5UcoH9eTVnDkChajzmUCego%3D&reserved=0>),
> even if it e.g., in
> essence, just states "Groovy runs/will run fine on GraalVM", "The
> Truffle license (GPL 2.0 w CP exception) is not compatible with Apache
> Groovy" or "Truffle makes no sense for Groovy (at this point)"...
>
> Cheers,
> mg
>
> This email message and any attachments are for the sole use of the
> intended recipient(s). Any unauthorized review, use, disclosure or
> distribution is prohibited. If you are not the intended recipient, please
> contact the sender by reply email and destroy all copies of the original
> message and any attachments.
>

Mime
View raw message