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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • Delgarde
    Senior Member
    • Apr 2010
    • 1692

    #11
    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.

    Comment

    • bug77
      Senior Member
      • Dec 2009
      • 6521

      #12
      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.

      Comment

      • elatllat
        Senior Member
        • Apr 2019
        • 573

        #13
        Originally posted by bug77 View Post
        ... RAM, the Java version...
        Have you tested GraalVM native?

        Comment

        • bug77
          Senior Member
          • Dec 2009
          • 6521

          #14
          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).

          Comment

          • caligula
            Senior Member
            • Jan 2014
            • 3342

            #15
            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?

            Comment

            • bug77
              Senior Member
              • Dec 2009
              • 6521

              #16
              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)

              Comment

              Working...
              X