Eclipse OpenJ9 0.27 Released For OpenJDK 8/11/16 Alternative

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • bug77
    replied
    Originally posted by caligula View Post
    Isn't GraalVM designed for those use cases where you need low memory footprint? I know it doesn't work too well with all the projects, but some modern frameworks like Quarkus should support it from day one.
    You're making a confusion here. GraalVM is not meant to be low footprint, it's meant to be polyglot. The native-image part of the project is supposed to enable AoT compile, which results in properly executable code and lower foot print. But native-image has been spun out of GraalVM and isn't even shipped by default anymore.

    Originally posted by caligula View Post
    Well, Docker supports layers. Are you saying the uppermost layer consisting of Java jar/class files is 20x bigger?
    I was talking about the finished product, the one that actually runs.
    Plus, it's just jdk-slim+my code. Because I didn't manage to get jlink working with Micronaut (I'll circle back at some point)

    Leave a comment:


  • caligula
    replied
    Originally posted by bug77 View Post

    Yeah, Java in the cloud, don't get me started. I've just compared something relatively simple written in Go and translated in Java. Where Go needs 25MB RAM, the Java version (with Micronaut), needs just under 280MB.
    Isn't GraalVM designed for those use cases where you need low memory footprint? I know it doesn't work too well with all the projects, but some modern frameworks like Quarkus should support it from day one.

    The Docker image is also almost 20x bigger.
    Well, Docker supports layers. Are you saying the uppermost layer consisting of Java jar/class files is 20x bigger?

    Leave a comment:


  • bug77
    replied
    Originally posted by elatllat View Post

    Have you tested GraalVM native?
    No, it's not production ready. I've tried it a couple of times before, it failed (because of one jar or another).

    Leave a comment:


  • elatllat
    replied
    Originally posted by bug77 View Post
    ... RAM, the Java version...
    Have you tested GraalVM native?

    Leave a comment:


  • bug77
    replied
    Originally posted by Delgarde View Post

    More so than they used to. On traditional big servers with legacy JavaEE apps, you're certainly correct - but for "cloud" architectures of clustered containers, I think there's more tolerance for updating more regularly, so the six-month support period isn't such a limit.
    Yeah, Java in the cloud, don't get me started. I've just compared something relatively simple written in Go and translated in Java. Where Go needs 25MB RAM, the Java version (with Micronaut), needs just under 280MB. The Docker image is also almost 20x bigger.

    Leave a comment:


  • Delgarde
    replied
    Originally posted by bug77 View Post
    Enterprises don't touch non-LTS Java, that only supported for 6 months.
    More so than they used to. On traditional big servers with legacy JavaEE apps, you're certainly correct - but for "cloud" architectures of clustered containers, I think there's more tolerance for updating more regularly, so the six-month support period isn't such a limit.

    Leave a comment:


  • bug77
    replied
    Originally posted by caligula View Post
    How would they support unreleased versions?
    "Released" doesn't mean anything in this context, because we're looking at an alternative implementation. J9 would only need to support the same JEPs OpenJDK does.
    Originally posted by caligula View Post
    Besides the LTS part doesn't mean anything. They'll release new OpenJDK versions every 6 months. You'll only get any kind of long term support by buying the commercial build.
    Enterprises don't touch non-LTS Java, that only supported for 6 months. All non-LTS releases have a big, big problem: they're supposed to be testing releases, but because enterprise won't touch them, they generate very little feedback.

    Anyway, it seems I judged them too early, support for 17 is coming this September: https://www.eclipse.org/openj9/docs/openj9_support/

    Leave a comment:


  • caligula
    replied
    Originally posted by bug77 View Post
    Also, a brilliant move offering Java 16 (non-LTS) support a couple of months before the release of Java 17 (LTS).
    How would they support unreleased versions? Besides the LTS part doesn't mean anything. They'll release new OpenJDK versions every 6 months. You'll only get any kind of long term support by buying the commercial build.

    Leave a comment:


  • bug77
    replied
    Yeah, pretty funny claiming "high performance" when you only have a handful of implementations out there (3, I believe, including this one).

    Also, a brilliant move offering Java 16 (non-LTS) support a couple of months before the release of Java 17 (LTS).

    Leave a comment:


  • blacknova
    replied
    When I tested it with a large project it was a lot slower than HotSpot, but I'd guess large applications are not a target use for OpenJ9 with it's main focus being fast startup.

    Leave a comment:

Working...
X