Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Eclipse OpenJ9 – Open-source JVM

github.com

Post reply on HN
Print view View original

101–105 of 105 posts

Re: Eclipse OpenJ9 – Open-source JVM

#101

Post by lambdadmitry »

ledgerdev wrote: post #49

Let's get straight to the really important question, can J9 or AOT help maybe just a little with clojure startup time woes?

Benchmark results aside, JVM has very little to do with the startup time. Most of the time is spent wiring Clojure namespaces together: every namespace must be evaluated, every Var initialized. That takes time. The core reason for that is that namespaces and vars are dynamic, not immutable, and Clojure runtime has to evaluate everything on each startup to uphold language semantics.

Re: Eclipse OpenJ9 – Open-source JVM

#102

Post by rservant »

filereaper wrote: post #56
nickhalfasleep wrote: post #53

Earlier quoted context omitted.

What is the 9 for? Jackknife? Jabbering?

There's some mythology here, perhaps another J9 greybeard can answer. The story I've heard so far goes as follows... There was some constant for 8K that was mistyped incorrectly, something like instead of: #define 8K 8192 They mistyped and wrote: #define 8K 8096 This caused all sorts of bugs and was known internally as the 8K bug. When time came to write the Java VM, they wanted to name it as "post 8k bug" they named…

This close, but not right. Dogs never entered into the equation. I'll post a blog somewhere with the history and come back here with a link.

Re: Eclipse OpenJ9 – Open-source JVM

#103

Post by rservant »

filereaper wrote: post #56
nickhalfasleep wrote: post #53

Earlier quoted context omitted.

What is the 9 for? Jackknife? Jabbering?

There's some mythology here, perhaps another J9 greybeard can answer. The story I've heard so far goes as follows... There was some constant for 8K that was mistyped incorrectly, something like instead of: #define 8K 8192 They mistyped and wrote: #define 8K 8096 This caused all sorts of bugs and was known internally as the 8K bug. When time came to write the Java VM, they wanted to name it as "post 8k bug" they named…

Here's the true story: https://medium.com/@rservant/how-did-the-j9-in-openj9-get-it...

Re: Eclipse OpenJ9 – Open-source JVM

#104

Post by DannyB2 »

inamberclad wrote: post #29
notimetorelax wrote: post #9

The "Welcome to the Eclipse OpenJ9 repository" is just brilliant. So many product blogs and source code repositories fail to introduce the product first.

I'm confused. Do you think they're doing it right with that as an intro?

There have been a few projects that followed a link to, possibly from this site, looked at for one to two minutes, and quit looking after being unable to even figure out what the project is, what it does, and whether I should be interested in it.

Re: Eclipse OpenJ9 – Open-source JVM

#105

Post by tmzt »

Any chance of an official unikernel distribution, or single entry-point mechanism for container images.

This along with AOT cached classes being baked into a vm/container image would be interesting.

Post reply on HN