undefined | Better HN

story

0 pointsjashmatthews5y ago0 comments

The CRuby JIT is stable but whether it improves performance or not is workload dependent.

It's simple not primitive. MJIT is designed to take advantage of a C compilers optimization.

"Compile to C" worked for Chicken Scheme for the past 20 years and continues to be a popular way for functional langauges to compile. It's also how Nim works. It's all about different trade-offs.

0 comments

pizza2345y ago

Are there any benchmarks available? It seems I can find very little (OptCarrot, some microbenchmarks, and some general assessments about usage with Rails), and a broad(er) overview is crucial to assess the overall performance (I suppose that you can have workloads where the performance degrades).

oblio5y ago

Chicken Scheme compiles ahead of time, doesn't it?

jashmatthewsOP5y ago

Yeah but it's not an important distinction.

oblio5y ago

Isn't it? Compiling C takes time, with Ruby you would be doing it for each execution. Is there some catching involved?

jashmatthewsOP5y ago

Almost everything is in a pre-compiled header. Its actually similar overhead to an LLVM based JIT.

You wouldn’t want to do it for a browser JIT but for a server side app it’s OK.

1 more reply

pansa25y ago

Nim does too.